Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add dkharlanau/agent-ready-web-profile --skill arwp-agent-discoverygit clone --depth 1 https://github.com/dkharlanau/agent-ready-web-profileWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/dkharlanau/agent-ready-web-profile/arwp-agent-discovery)<a href="https://agentmods.dev/skills/dkharlanau/agent-ready-web-profile/arwp-agent-discovery"><img src="https://agentmods.dev/badge/skills/dkharlanau/agent-ready-web-profile/arwp-agent-discovery/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dkharlanau/agent-ready-web-profile/arwp-agent-discovery"><img src="https://agentmods.dev/badge/skills/dkharlanau/agent-ready-web-profile/arwp-agent-discovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00088 | $0.00772 |
| Opus 5 | $0.00044 | $0.00386 |
| Sonnet 5 | $0.00018 | $0.00154 |
| Haiku 4.5 | $0.00009 | $0.00077 |
Grade A, and why
arwp-agent-discovery scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ARWP Agent Discovery
Use this skill to make a website easier for agents to discover and operate without inventing a competing protocol or fake capability.
Decision order
Prefer existing upstream mechanisms before adding ARWP-native metadata:
- ordinary semantic HTML and stable canonical URLs;
- OpenAPI / RFC API Catalog where real APIs exist;
- Agent Skills for reusable procedures;
- A2A Agent Card for real agent endpoints;
- MCP metadata/runtime for actual MCP servers;
- WebMCP only for real browser-exposed tools;
- ARD for agentic-resource discovery when appropriate;
- ARWP publisher profile as an optional service map tying real surfaces together.
Workflow
-
Inventory actual interfaces.
- Search code/config for API routes, OpenAPI, MCP, A2A, skills, WebMCP, feeds, search endpoints, data exports and auth metadata.
- Distinguish documentation mentioning a protocol from an implemented capability.
-
Add lightweight readability surfaces.
llms.txt: concise canonical routes/resources; do not duplicate the whole site.AGENTS.md: repository instructions for coding agents when developer-facing.sitemap.md: optional compact navigation map.- Preserve normal XML sitemap/canonical SEO independently.
-
Add Agent Skills for repeatable tasks.
- Folder name is kebab-case.
- File must be exactly
SKILL.md. - Frontmatter must include
nameand trigger-richdescription. - Keep the main skill concise and use
references/,scripts/, orassets/for progressive disclosure. - Skills should execute a real workflow, not merely restate documentation.
-
Add structured discovery only where backed by implementation.
- OpenAPI URLs must describe real endpoints.
- A2A discovery URLs are metadata; do not treat a card URL as the callable endpoint unless the spec says so.
- MCP server cards/metadata are evidence, not authorization.
- ARD resources are discovery evidence; relevance is not trust.
- Never expose internal/private endpoints in public discovery files.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 74 lines · 88 tokens per session scan A 5e4d8c0784ec
arwp-agent-discovery is a skill published in the GitHub repository dkharlanau/agent-ready-web-profile (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 88 tokens to every session and 772 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.
Other skills, from other repositories
acp-checkout-rest
Implement the ACP REST checkout API — create, update, retrieve, complete, and cancel checkout sessions. Use when building merchant-side checkout endpoints, handling the checkout session state machine, or integrating with AI agent checkout flows.
a2a-client
Build an A2A client — the agent-side code that discovers other agents, sends tasks, handles responses, and manages multi-turn conversations. Use when implementing the client side that delegates work to A2A agents.
a2a-jsonrpc-transport
Implement the A2A JSON-RPC 2.0 transport layer — request/response format, method routing, batch requests, and HTTP details. Use when building custom A2A transport handling or debugging protocol-level issues.
a2a-mcp-bridge
Build bridges between A2A and MCP — wrap A2A agents as MCP tools, use MCP tools from A2A agents, and architect hybrid multi-agent systems. Use when integrating A2A agent-to-agent communication with MCP tool access.
a2a-server
Build an A2A server — the agent-side endpoint that receives JSON-RPC requests, processes tasks, manages state, and returns results. Use when implementing the server side of an A2A agent.
a2a-streaming
Implement A2A SSE streaming — message/stream method, Server-Sent Events, TaskStatusUpdateEvent, TaskArtifactUpdateEvent, and re-subscription. Use when building real-time streaming responses in A2A agents.