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 agentmods add skills/ea-toolkit/architecture-catalog/crawl-apisnpx skills add ea-toolkit/architecture-catalog --skill crawl-apisgit clone --depth 1 https://github.com/ea-toolkit/architecture-catalogWrote 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/ea-toolkit/architecture-catalog/crawl-apis)<a href="https://agentmods.dev/skills/ea-toolkit/architecture-catalog/crawl-apis"><img src="https://agentmods.dev/badge/skills/ea-toolkit/architecture-catalog/crawl-apis.svg" alt="Measured on agentmods" 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.00041 | $0.01229 |
| Opus 5 | $0.00020 | $0.00615 |
| Sonnet 5 | $0.00008 | $0.00246 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
crawl-apis 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 6d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crawl APIs — Discover and Register API Definitions
Scan a codebase directory for API definitions and propose registry entries.
Arguments
$1— Path to scan (required). Absolute or relative path to the codebase to crawl.--domain <name>— Domain to assign discovered APIs to (optional, will ask if omitted).--write— Write proposed entries to registry immediately (default: preview only).
If no path is provided, ask the user which directory to scan.
Workflow
1. Discover Type-to-Folder Mapping
Read models/registry-mapping.yaml to find:
- The folder path for
api_contractentries - The folder path for
api_endpointentries - The
_template.mdin each folder for frontmatter structure
Never hardcode paths. Always derive from the YAML.
2. Scan for API Definitions
Search the target directory for API-related files. Use these detection patterns:
OpenAPI / Swagger specs:
# Find OpenAPI/Swagger YAML and JSON files
- Glob:
**/{openapi,swagger}*.{yaml,yml,json},**/api-spec*.{yaml,yml,json} - Content match: files containing
openapi:orswagger:at the top level
REST route definitions (Node.js/Express/Fastify/Hono):
- Grep for patterns:
router\.(get|post|put|delete|patch),app\.(get|post|put|delete|patch),@Get|@Post|@Put|@Delete(NestJS decorators) - Look in:
**/routes/**,**/controllers/**,**/handlers/**,**/api/**
GraphQL schemas:
- Glob:
**/*.graphql,**/*.gql - Content match: files containing
type Query,type Mutation,schema {
gRPC / Protobuf:
- Glob:
**/*.proto - Content match:
service <Name>blocks
Python (FastAPI/Flask/Django REST):
- Grep for:
@app.route,@router.get|post|put|delete,@api_view,class.*ViewSet
3. Extract API Information
For each discovered API, extract:
| Field | Source |
|---|---|
name |
OpenAPI info.title, route prefix, GraphQL type name, proto service name |
description |
OpenAPI info.description, JSDoc/docstring if available |
protocol |
REST, GraphQL, gRPC, async (inferred from file type) |
endpoints |
Individual route paths / operations / queries+mutations |
status |
draft (always — human reviews and promotes) |
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.
- 6d ago First seen · 136 lines · 41 tokens per session scan A 90b367ad04f7
crawl-apis is a skill published in the GitHub repository ea-toolkit/architecture-catalog (38 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 1,229 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
wordpress-plugin-to-emdash
Port a WordPress plugin to EmDash CMS. Use this skill when asked to migrate, convert, or port a WordPress plugin, theme functionality, or custom post type to EmDash. Provides concept mapping and implementation patterns.
emdash-cli
Use the EmDash CLI to manage content, schema, media, and more. Use this skill when you need to interact with a running EmDash instance from the command line — creating content, managing collections, uploading media, generating types, or scripting CMS operations.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
ux-acceptance-tester
Perform a goal-driven, black-box UX acceptance journey in a browser and report the path, friction, and observable outcome. Use only in an isolated tester context with a supplied start URL and brief.
investigate
Investigate a single EmDash issue end to end -- classify, choose a repro path, reproduce, diagnose, verify, and (only on an explicit maintainer fix directive) fix and confirm. Every verdict carries its evidence.
fix
Implement diagnose's proposed fix when verify says bug, the cause is pinned, and a maintainer triggered a fix. Follow EmDash conventions, run focused checks, publish the candidate, and report the results accurately.