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/srstomp/pokayokay/docsgit clone --depth 1 https://github.com/srstomp/pokayokayWhat 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.00004 | $0.00460 |
| Opus 5 | $0.00002 | $0.00230 |
| Sonnet 5 | $0.00001 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
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 2d 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
Documentation Workflow
Create documentation for: $ARGUMENTS
Steps
1. Identify Documentation Type
From $ARGUMENTS, determine:
- README: Project overview and setup
- API docs: Endpoint reference
- ADR: Architecture Decision Record
- User guide: How-to instructions
- Contributing: Developer onboarding
- Changelog: Version history
2. Identify Audience
- Developers (internal team)
- External developers (API consumers)
- End users
- Operations team
3. Gather Information
- Read relevant code
- Interview stakeholders (if needed)
- Review existing docs
- Check issue tracker for common questions
4. Generate Documentation
For README:
- Project description
- Quick start
- Prerequisites
- Installation
- Usage examples
- Configuration
- Contributing link
For API Docs:
- Endpoint reference
- Request/response examples
- Authentication
- Error codes
- Rate limits
For ADR:
- Title and date
- Status (proposed/accepted/deprecated)
- Context (problem)
- Decision (solution)
- Consequences (trade-offs)
5. Review and Validate
- Technical accuracy
- Clarity for audience
- Complete examples
- Working code samples
6. Create Follow-up Tasks
npx @stevestomp/ohno-cli create "Docs: [specific doc]" -t docs
Covers
- README creation
- API documentation
- Architecture Decision Records (ADR)
- User guides and tutorials
- Developer onboarding
- Changelog management
Related Commands
/pokayokay:api- Document API design/pokayokay:arch- Document architecture/pokayokay:work- Implement documentation
Skill Integration
When documentation involves:
- API reference → Also load
api-designskill - Architecture docs → Also load
architecture-reviewskill - Database docs → Also load
database-designskill
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.
- 2d ago First seen · 90 lines · 4 tokens per session scan A 6d90acaf5e82
docs is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 1mo ago), licensed MIT. It adds 4 tokens to every session and 460 once invoked, about $0.0000 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.