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/archgit 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.00006 | $0.01105 |
| Opus 5 | $0.00003 | $0.00553 |
| Sonnet 5 | $0.00001 | $0.00221 |
| Haiku 4.5 | $0.00001 | $0.00111 |
Grade A, and why
arch 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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Review Workflow
Review architecture of: $ARGUMENTS
Mode Detection
Parse $ARGUMENTS to determine mode:
--auditflag present → Architecture audit mode (creates tasks for issues)- No flag → Review/planning mode (default behavior)
Steps
1. Analyze Structure
- Directory organization
- Module boundaries
- Layer separation
2. Map Dependencies
- Import relationships
- Circular dependencies
- External dependencies
3. Evaluate Patterns
- Consistency across codebase
- Adherence to conventions
- Code organization
4. Identify Issues
Severity levels:
- Critical: Blocking or causing bugs
- Major: Technical debt accumulating
- Minor: Style/consistency issues
- Info: Suggestions for improvement
5. Plan Refactoring
- Prioritize by impact
- Define migration path
- Estimate effort
6. Create Tasks
npx @stevestomp/ohno-cli create "Refactor [area]" -t chore
Audit Mode (--audit flag)
When --audit is specified, switch to architecture audit mode that automatically creates tasks:
Audit Steps
- Scan Architecture Analyze codebase for:
- Circular dependencies
- Layer violations (UI importing from data layer directly)
- God classes/modules (too many responsibilities)
- Orphaned code (unreachable/dead code)
- Security architecture issues
- Classify Issues
| Issue Type | Description | Priority | Task Type |
|---|---|---|---|
| Security flaw | Auth bypass, insecure patterns | P0 | bug |
| Circular dependency | Blocking clean builds/tests | P1 | chore |
| Layer violation | Breaks separation of concerns | P1 | chore |
| Feature blocker | Architecture blocking feature dev | P1 | chore |
| God module | >500 lines, many responsibilities | P2 | chore |
| Dead code | Unreachable, unused exports | P3 | chore |
| Inconsistency | Naming, patterns, conventions | P3 | chore |
- Calculate Impact For each issue, assess:
- Blast radius: How many modules affected?
- Change risk: How risky is the fix?
- Blocking: Is this blocking other work?
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 · 159 lines · 6 tokens per session scan A ba8598651355
arch is a command published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 1,105 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.