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 commands/amey-thakur/ai-skills/api-docs-from-codegit clone --depth 1 https://github.com/Amey-Thakur/AI-SKILLSWrote 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/commands/amey-thakur/ai-skills/api-docs-from-code)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/api-docs-from-code"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/api-docs-from-code.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 | $0.00015 | $0.00333 |
| Opus 5 | $0.00008 | $0.00167 |
| Sonnet 5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
api-docs-from-code 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.
What it actually says
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
Write reference documentation for the API below, for {audience}.
For each endpoint or public function:
- Name and purpose: one sentence on what it does for the caller.
- Signature: method and path (or function signature), parameters with types, which are required, and defaults where the code shows them.
- Request example: one realistic call, using only field names present in the code.
- Response: the success shape with field meanings, plus each error the code actually returns (status, condition, body shape).
- Notes: auth requirements, rate limits, idempotency, pagination, but only where the code or its middleware shows them.
Rules:
- Document what the code does, not what it should do. Where behavior is unclear from the code alone, write [verify: question] rather than guessing.
- Keep descriptions to the caller's perspective; internals stay out unless they leak into behavior.
- Order endpoints by resource, then by the natural usage sequence.
- End with a "Not documented" list naming anything you skipped and why.
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 · 41 lines · 15 tokens per session scan A f6aa1a58ff1d
api-docs-from-code is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (7 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 333 once invoked, about $0.0001 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-31.
Other commands, from other repositories
ui5-version
Display UI5 version information, support status, release notes, and upgrade paths.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.