wshoffner.dev valid
wshoffner.dev
Personal workshop of Wes Shoffner, infrastructure engineer and founder of
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T21:47:05.757Z. Cached copy · Source on wshoffner.dev
# wshoffner.dev
> Personal workshop of Wes Shoffner, infrastructure engineer and founder of
> Clocktower and Associates. Writing about AI agents, MCP servers and
> infrastructure, plus open-source projects and a terminal full of retro games.
The site presents itself as WesOS, a three-panel desktop shell, but every page
is server rendered and readable without JavaScript. Structured capabilities,
navigation and access policy are published separately at
https://www.wshoffner.dev/.well-known/agents.json
Agents are invited to sign the guestbook: POST a JSON body of
{"who": "your name", "msg": "your message"} to
https://www.wshoffner.dev/api/agent/guestbook (no auth, one entry per IP per day, no
links). Full ACP tool definitions are in the services block of agents.json.
## Writing
- [How Do You Keep Agents From Lying? Create a Source of Truth.](https://www.wshoffner.dev/blog/how-do-you-keep-agents-from-lying-create-a-source-of-truth): I sent 78 autonomous agents against my own website and refused to believe a single thing they told me. Every success claim needed a cryptographic receipt from the server. Here's what the receipts caught, and why I think response signing is the cheapest trust infrastructure you can build.
- [I Tried to Prove Agent-Readiness Saves Tokens. 52 Runs Later, I Can't.](https://www.wshoffner.dev/blog/i-tried-to-prove-agent-readiness-saves-tokens-52-runs-later-i-cant): I built a scanner that grades repos on how readable they are to AI agents, then ran a controlled experiment to see if any of it matters. The result is a null, plus three things I did not expect about how agents actually read your code.
- [I Put One Example in a Prompt and It Decided How the Agent Read My Whole Repo](https://www.wshoffner.dev/blog/i-put-one-example-in-a-prompt-and-it-decided-how-the-agent-read-my-whole-repo): I was benchmarking agent-readiness when I noticed the agent never opened a single markdown file. Not the README, not AGENTS.md, nothing. The cause was one helpful sentence I wrote in the prompt.
- [Your Phone as a Terminal: One Command, One QR Code, No SSH Client](https://www.wshoffner.dev/blog/termbeam): A code review of TermBeam, a Node CLI that shares a local terminal to your phone over a QR code — no SSH, no port forwarding, no static IP.
- [htop for Your Git History](https://www.wshoffner.dev/blog/gittop): A code review of gittop, a Go TUI that turns a dozen git log incantations into a seven-tab dashboard — with a participle-based filter language and braille-rendered charts. I wrote the project's first 22 stats tests and opened the PR.
- [What's Actually in Your Docker Image? Reading the Parser That Tells You](https://www.wshoffner.dev/blog/xray): A Rust TUI that inspects multi-gigabyte Docker images using 80 MB of RAM where dive chokes. I read the streaming tar-in-tar parser, wrote the project's first 55 unit tests, and got them merged same day.
- [When AI Writes Your Firewall, Check the Math](https://www.wshoffner.dev/blog/blackwall):
…
Machine-readable: GET /v1/resolve?q=wshoffner.dev · GET /v1/domain/wshoffner.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage wshoffner.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for wshoffner.dev:
1. POST https://agentwebmap.com/v1/sites/wshoffner.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://wshoffner.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/wshoffner.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/wshoffner.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.