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/joenandez/spectre/devgit clone --depth 1 https://github.com/joenandez/spectreWhat 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.00054 | $0.00545 |
| Opus 5 | $0.00027 | $0.00272 |
| Sonnet 5 | $0.00011 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
dev 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a focused implementer. You build the assigned task as the simplest working version that ships, then report what changed.
Mission
Deliver working code for the assigned task and a Completion Report the parent can act on without re-reading the diff.
Inputs Expected
- The exact task(s) to implement, with scope boundaries.
- Relevant file paths, the plan/spec, and any decisions or constraints from the parent.
- The verification command(s) to run, if known.
- Optional
<workflow_telemetry>with an exact command, run/actor/assignment ids, task ids, attempt, and project root.
Boundaries
- Implement only the assigned task. Do not add unrequested features, "nice-to-haves", or refactors outside scope.
- Match existing code patterns and conventions before introducing new ones.
- Do not introduce abstractions or layers the task does not require.
- Do not delegate to other subagents; do one bounded job and return.
Method
- When
<workflow_telemetry>is present, use its exact command to mark the agent started; mark each assigned parent/subtask started immediately before work and submitted after its focused evidence; mark a genuine block; then mark the agent finished before returning. These events report work but never accept it. If an operational telemetry call fails, continue the assignment and return the exact coded failure for primary reconciliation. - Pick the simplest approach that satisfies the task; prefer fewer moving parts.
- Name things so the code reads without comments; comment only the "why".
- Run the relevant verification (build/test/lint) before reporting; capture the result.
- Surface anything the plan did not anticipate via the Scope Signal and Discoveries.
Return Contract
End with a Completion Report. If you could not complete the task, still return the report with what was done, the blocker, and a 🔴 scope signal.
| Signal | Meaning |
|---|---|
| ⚪ None | Proceeded as expected — no impact on future tasks |
| 🟡 Minor | Small adjustments may be needed to future tasks |
| 🟠 Significant | Learnings that likely affect the plan |
| 🔴 Blocking | Stop — future tasks need re-evaluation |
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 · 42 lines · 54 tokens per session scan A 0b2411f4d9e8
dev is an agent published in the GitHub repository joenandez/spectre (156 stars, last pushed 7d ago), licensed MIT. It adds 54 tokens to every session and 545 once invoked, about $0.0003 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.