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 agents/mystilleef/spae-framework/troubleshootgit clone --depth 1 https://github.com/mystilleef/spae-frameworkWrote 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/agents/mystilleef/spae-framework/troubleshoot)<a href="https://agentmods.dev/agents/mystilleef/spae-framework/troubleshoot"><img src="https://agentmods.dev/badge/agents/mystilleef/spae-framework/troubleshoot.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.00011 | $0.00078 |
| Opus 5 | $0.00005 | $0.00039 |
| Sonnet 5 | $0.00002 | $0.00016 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
troubleshoot 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
Role
Embody an expert software engineer. You specialize in troubleshooting and fixing issues.
Directives
- Always invoke the
troubleshootskill immediately, regardless of input. - Present result to main agent.
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 · 19 lines · 11 tokens per session scan A 9720503f9b6f
troubleshoot is an agent published in the GitHub repository mystilleef/spae-framework (1 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 78 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 agents, from other repositories
i18n
Hermex ships one String Catalog, HermesMobile/Resources/Localizable.xcstrings, included in the app, widget, and share-extension targets. Every user-facing literal is already externalized (String(localized:) / LocalizedStringKey), so adding a language is normally translation-only — no Swift edits.
feature-gap-index
Thin, always-current classification of upstream Hermes-WebUI API route groups against Hermes-Mobile. This file replaces an earlier 1,400-line per-endpoint catalog, which mixed durable judgment (priority, defer/skip decisions, safety notes) with volatile detail (exact JSON shapes, handler names) that rotted between…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for issue operations.
lead
Agent "lead" from enmanuelmag/agent-harness-kit, covering lead agent — @cardor/agent-harness-kit, available research tools, provider delegation guidance, lead agent — @cardor/agent-harness-kit and !! absolute constraint — read before anything else !!.
builder
gent to implement code changes for a task that has already been planned by lead and analyzed by explorer. The builder writes, edits, and creates files based on the plan and the explorer's analysis. Invoke only after the explorer has completed its action. Never invoke without a canonical handoff addressed to builder.
explorer
gent to read and map the codebase for a specific task. The explorer researches relevant files, understands existing patterns, and produces a structured analysis for the builder to use. Invoke after the lead has defined a plan and before the builder starts. Never invoke for tasks that require writing or modifying files.