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 skills add markmhendrickson/neotoma --skill fix-feature-buggit 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/skills/markmhendrickson/neotoma/fix-feature-bug)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/fix-feature-bug"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/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/skills/markmhendrickson/neotoma/fix-feature-bug"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/fix-feature-bug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 6 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00008 | $0.00784 |
| Opus 5.5 | $0.00003 | $0.00314 |
| Sonnet 5.5 | $0.00002 | $0.00157 |
| Haiku 4.5 | $0.00001 | $0.00078 |
Grade A, and why
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.
Copies of this mod
2 near-identical copies found in the catalogue:
- fix-feature-bug — 92% identical, 9 lines differ
- fix_feature_bug — 91% identical, 17 lines differ
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: fix-feature-bug description: Fix bugs using structured workflow with error classification and regression tests. triggers:
- bug
- error
- fix
- broken
- not working
- failing
- fix-feature-bug
- /fix-feature-bug
Fix Feature Bug
Fix a bug in a feature or module.
Configuration is read from foundation-config.yaml.
This workflow can also be triggered automatically via .claude/rules/bug_fix_detection.md (or foundation/agent_instructions/cursor_rules/bug_fix_detection.md) when you mention bug/error-related patterns in natural language (e.g., "bug", "error", "fix", "broken"). Both paths execute the same workflow.
Workflow
-
Load configuration:
- Read
foundation-config.yamlfor bug fix settings - Check if error classification is configured
- Determine feature/module directory structure
- Read
-
Identify feature/module from error, path, or context.
-
Load relevant documents:
- Repository navigation guide (if configured)
- Feature/module spec and manifest (if available)
- Error classification documentation (if configured)
- Relevant subsystem/module documentation (if configured)
-
Classify bug (if error classification configured):
- Use configured error classification system
- Determine correction approach based on class
-
Apply correction rules:
- If Class 1 (Implementation bug): Patch code only
- If Class 2 (Spec bug): Update spec/manifest first, then align code/tests
- If Class 3 (Architectural bug): Update subsystem/architecture docs first, then rebuild
- If no classification: Fix bug and update relevant documentation
-
Always add a regression test.
-
Run tests:
- Run configured test commands
- Verify fix doesn't break existing functionality
-
Output:
- Error class (if classification configured)
- Reason for classification
- Corrected files
- Tests added/updated
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 · 108 lines · 8 tokens per session scan A a908367fcce2
fix-feature-bug is a skill published in the GitHub repository markmhendrickson/neotoma (34 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 784 once invoked, about $0.0000 per session on Opus 5.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-30.
Other skills, from other repositories
bernstein-alerts
Show active alerts from Bernstein - failed tasks, stalled agents, budget warnings, blocked tasks needing human intervention. Use when the user asks about problems, errors, warnings, or what needs attention.
ci-fixer
CI failures - read error, minimal fix, verify.
plumb-line-remediate
Use when applying findings from a plumb-line audit report — the builder has a report (or pasted findings) and wants the fixes made. Opt-in and separate from the audit, which is read-only and never fixes.
cratis-chronicle-cli-operations
Inspect and operate a running Chronicle server with the cratis CLI - contexts and connection resolution, machine-readable output, failed partitions, observers, event sequences, read models, projections and jobs, and the authorization discipline for replay, retry, quarantine clearing and other mutations. Use when the…
cratis-lens-browser-extension
Use the Cratis Lens browser extension against a running Cratis Arc application — building and side-loading it, what the Arc app must already serve for Lens to work, switching the active user and tenant, and executing a command or query from the popup. Use when setting Lens up, when Lens does not detect an Arc app, or…
cratis-arc-observable-query-http
Inspect a Cratis Arc observable query from a terminal with curl or another plain HTTP client — snapshot GET, waiting for the first result, Server-Sent Events streaming, and long polling, plus the exact query-string keys, status codes, and payload shape. Use when debugging or exploring an observable query without…