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/markmhendrickson/neotomaWrote 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/markmhendrickson/neotoma/foundation_fix_feature_bug)<a href="https://agentmods.dev/commands/markmhendrickson/neotoma/foundation_fix_feature_bug"><img src="https://agentmods.dev/badge/commands/markmhendrickson/neotoma/foundation_fix_feature_bug/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/markmhendrickson/neotoma/foundation_fix_feature_bug"><img src="https://agentmods.dev/badge/commands/markmhendrickson/neotoma/foundation_fix_feature_bug.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.00014 |
| Opus 5.5 | $0.00000 | $0.00006 |
| Sonnet 5.5 | $0.00000 | $0.00003 |
| Haiku 4.5 | $0.00000 | $0.00001 |
Grade A, and why
foundation_fix_feature_bug 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.
This is a copy
100% identical to fix_feature_bug — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
../../foundation/agent_instructions/cursor_commands/fix_feature_bug.md
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 · 1 lines · 0 tokens per session scan A 84f282a60ab8
foundation_fix_feature_bug is a command published in the GitHub repository markmhendrickson/neotoma (34 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 14 tokens. A static security scan graded it A with 0 findings. It is 100% identical to fix_feature_bug, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
code-semantic-search
Semantic code search using vector embeddings and hybrid search.
performance-optimization
Optimize application performance end-to-end using specialized performance and optimization agents.
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.