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.
git clone --depth 1 https://github.com/neurofoo/agent-skillsWrote 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/neurofoo/agent-skills/prepare)<a href="https://agentmods.dev/commands/neurofoo/agent-skills/prepare"><img src="https://agentmods.dev/badge/commands/neurofoo/agent-skills/prepare/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/neurofoo/agent-skills/prepare"><img src="https://agentmods.dev/badge/commands/neurofoo/agent-skills/prepare.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00795 |
| Opus 5.5 | $0.00000 | $0.00318 |
| Sonnet 5.5 | $0.00000 | $0.00159 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
prepare 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 1mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare to Be Wrong
Counter overconfidence by planning for both success and failure. Set tripwires and fallbacks before you need them.
Instructions
Assume you might be wrong. Plan for how you'll detect problems and what you'll do. This isn't pessimism—it's preparedness.
Output Format
Decision/Plan: [What you've decided to do]
Premortem
Imagine this decision failed completely. What happened?
It's 6 months later. This was a disaster. Looking back, what went wrong?
| Failure Mode | Likelihood | Severity | Was It Predictable? |
|---|---|---|---|
| [what failed] | High/Med/Low | High/Med/Low | [Yes/No] |
| [what failed] | High/Med/Low | High/Med/Low | [Yes/No] |
| [what failed] | High/Med/Low | High/Med/Low | [Yes/No] |
Which failures can we prevent now?
| Failure | Prevention |
|---|---|
| [failure] | [how to prevent it] |
| [failure] | [how to prevent it] |
Bookend the Future
Best realistic case:
If everything goes well, what does success look like? [Description]
Worst realistic case:
If things go badly, what does failure look like? [Description]
Are we prepared for the worst case? [Yes/No/Partially]
What would make the worst case more survivable?
- [Mitigation 1]
- [Mitigation 2]
Set Tripwires
Decide in advance what would cause you to reconsider
| Tripwire | Trigger Condition | Action If Triggered |
|---|---|---|
| Date | [specific date to review] | [reassess decision] |
| Metric | [if X drops below Y] | [specific action] |
| Event | [if specific thing happens] | [specific action] |
| Resource | [if we spend more than X] | [stop and evaluate] |
Tripwire reminder set? [Where/how will you be reminded?]
Safety Net
If we're wrong, what's our fallback?
| If This Happens | Our Response |
|---|---|
| [scenario 1] | [fallback plan] |
| [scenario 2] | [fallback plan] |
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.
- 1mo ago First seen · 121 lines · 0 tokens per session scan A 9d34a6006619
prepare is a command published in the GitHub repository neurofoo/agent-skills (122 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 795 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-30.
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.