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/valsecchi75/project-scaffolder/errorgit clone --depth 1 https://github.com/valsecchi75/project-scaffolderWhat 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.00029 | $0.00401 |
| Opus 5 | $0.00015 | $0.00200 |
| Sonnet 5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
error 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
/error
Log a bug or error with full propagation to guardrails and connected skills.
Usage
/error <short title>
Examples
/error DateFormat crashes on Android 11 with IT locale
/error Isar schema migration fails when switching device
/error Push notification silently dropped on MIUI devices
Prompt flow
- Context: what were you doing when it happened?
- Error: what went wrong? (paste stack trace if available)
- Root cause: what was the real problem? (not the symptom)
- Fix: how was it resolved?
- Affected skills: which skills are relevant? (infer from domain, confirm with user)
Atomic operations
- Append to
wiki/debugging/known-errors.md:## KE-NNN: <title> **Date:** YYYY-MM-DD **Context:** ... **Error:** ... **Root cause:** ... **Fix:** ... - Append to
guardrails/errors-to-avoid.md:## ERR-NNN: <title> **Pattern to avoid:** ... **Correct pattern:** ... **Skills affected:** [list] **Ref:** KE-NNN - Call Synapse Operation 3 to propagate to affected skills.
Rules
ERR-NNNandKE-NNNauto-increment independently.- Always cross-reference
KE↔ERR. - If the error has no identified root cause yet: log with status
[INVESTIGATING], refuse Synapse propagation until root cause is known. - Never delete prior entries — even if the error was mis-categorized, mark as superseded.
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 · 59 lines · 29 tokens per session scan A 5d505513efff
error is a command published in the GitHub repository valsecchi75/project-scaffolder (9 stars, last pushed 29d ago), licensed MIT. It adds 29 tokens to every session and 401 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
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.