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/iwritec0de/app-dev/docsgit clone --depth 1 https://github.com/iwritec0de/app-devWhat 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.00010 | $0.00776 |
| Opus 5 | $0.00005 | $0.00388 |
| Sonnet 5 | $0.00002 | $0.00155 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
docs 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 yesterday.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Docs
Generate or update an OpenAPI 3.1 specification from existing API routes.
Load the api-design skill for REST conventions and OpenAPI patterns.
Usage
/docs [--output openapi.yaml] [--format yaml|json]
Arguments
Parse $ARGUMENTS to extract:
- --output (optional, default:
openapi.yaml) — Output file path - --format (optional, default:
yaml) — Output format
Instructions
1. Find All API Routes
Scan the project for route definitions based on framework:
Express/Fastify/Koa:
grep -rn "router\.\(get\|post\|put\|patch\|delete\)" --include="*.ts" --include="*.js"
grep -rn "app\.\(get\|post\|put\|patch\|delete\)" --include="*.ts" --include="*.js"
Next.js App Router:
find app/api -name "route.ts" -o -name "route.js"
FastAPI/Flask/Django:
grep -rn "@app\.\(get\|post\|put\|delete\)\|@router\." --include="*.py"
grep -rn "path\(" --include="*.py" # Django
Go:
grep -rn "HandleFunc\|Handle\|Get\|Post\|Put\|Delete" --include="*.go"
2. Analyze Each Endpoint
For each route found, read the handler to determine:
- HTTP method and path
- Request body schema (from validation or types)
- Query parameters
- Path parameters
- Response schema (from return types or response calls)
- Authentication requirements
- Error responses
3. Generate OpenAPI Spec
openapi: 3.1.0
info:
title: <project-name> API
version: <from-package.json>
description: <auto-generated>
servers:
- url: http://localhost:<port>
description: Development
paths:
/api/resource:
get:
summary: List resources
tags: [Resource]
parameters:
- name: page
in: query
schema:
type: integer
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/ResourceList'
components:
schemas:
Resource:
type: object
properties:
id:
type: string
format: uuid
securitySchemes:
bearerAuth:
type: http
scheme: bearer
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.
- yesterday First seen · 128 lines · 10 tokens per session scan A 3f64e53d767f
docs is a command published in the GitHub repository iwritec0de/app-dev (3 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 776 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
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.
better-auth:add-plugin
Add a better-auth plugin to an existing project. Configures server and client plugins with proper imports.
sheet-report
Analyze a Numbers or Excel file and generate a report with charts.
numbers-to-excel
Convert a Numbers document to Excel.
prompt
System instructions for writing effective prompts. Apply when generating commands, skills, agents, or any LLM instructions.
add-skill
Add a new Skill to the current plugin with proper structure.