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/adewale/keyboardia/post-fixgit clone --depth 1 https://github.com/adewale/keyboardiaWrote 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/adewale/keyboardia/post-fix)<a href="https://agentmods.dev/commands/adewale/keyboardia/post-fix"><img src="https://agentmods.dev/badge/commands/adewale/keyboardia/post-fix.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.00000 | $0.00448 |
| Opus 5 | $0.00000 | $0.00224 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
post-fix 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 3d 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
Post-Fix Analysis Command
A bug has been fixed. Now perform a comprehensive post-fix analysis to find similar issues across the codebase.
Instructions
-
Understand the fix: Ask the user (or infer from recent conversation) what the bug was and what pattern caused it.
-
Extract the pattern: Identify:
- The code pattern that caused the bug (e.g.,
getInstance(),setTimeout without cleanup) - Any risky context that makes the pattern dangerous (e.g.,
Tone.,audioContext) - The file that was fixed
- The code pattern that caused the bug (e.g.,
-
Run the post-fix analysis tool:
cd /Users/ade/Documents/projects/tunejs_implementation/keyboardia/app && npx tsx scripts/post-fix-analysis.ts \ --pattern "PATTERN_HERE" \ --risky-context "CONTEXT_HERE" \ --file "FIXED_FILE" \ --symptom "SYMPTOM" -
Review high-risk matches: For any matches marked as HIGH RISK:
- Read the affected files
- Determine if they have the same bug
- Report findings to the user
-
Update documentation if warranted: If this is a new bug pattern:
- Consider adding to
src/utils/bug-patterns.ts - Consider adding to
docs/DEBUGGING-LESSONS-LEARNED.md - Use
npx tsx scripts/bug-capture.ts --interactiveif detailed capture needed
- Consider adding to
-
Report to user:
- How many similar patterns were found
- Which are high risk and need review
- Recommendations for prevention
Example Usage
User: "I fixed a singleton bug in engine.ts where getInstance() was caching Tone.js nodes"
Response:
- Run post-fix analysis with pattern
getInstance\(\)and risky contextTone\. - Review matches in audio/ directory
- Report findings
Arguments
$ARGUMENTS - Optional: Description of the bug that was fixed (pattern, file, symptom)
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.
- 3d ago First seen · 50 lines · 0 tokens per session scan A 0fd19ab4c894
post-fix is a command published in the GitHub repository adewale/keyboardia (3 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 448 tokens. 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.
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.