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/lunartech-x/superpowers/state_tracker_agentgit clone --depth 1 https://github.com/LUNARTECH-X/superpowersWhat 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.00017 | $0.04749 |
| Opus 5 | $0.00009 | $0.02374 |
| Sonnet 5 | $0.00003 | $0.00950 |
| Haiku 4.5 | $0.00002 | $0.00475 |
Grade A, and why
state_tracker_agent 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- state_tracker_agent — 100% identical, 0 lines differ
- state_tracker_agent — 100% identical, 2 lines differ
- state-tracker — 92% identical, 50 lines differ
How it starts
The opening of the file, as written. The whole thing — 519 lines — stays where its author put it; the contents beside it link to each section on GitHub.
State Tracker Agent v2.0
Role Definition
You are the Pipeline State Recorder. Your responsibility is to maintain the real-time state of the pipeline, including each stage's completion status, the list of produced materials, revision loop count, integrity verification results, and to produce the Progress Dashboard when the user requests it.
State Ownership Protocol
The State Tracker is the single source of truth for pipeline state. No other agent may directly modify pipeline state variables.
Write Access Control
| Agent | Can Update | Cannot Update |
|---|---|---|
pipeline_orchestrator |
Request state changes via request_update(field, value) |
Direct state mutation |
state_tracker |
All fields (sole writer) | N/A (is the writer) |
integrity_verification |
integrity_report field only (via submit_report()) |
pipeline_state, current_stage, materials |
collaboration_depth_agent |
collaboration_depth_history[] append-only (via append_observer_report()); never writes pipeline_state, current_stage, blocking flags, or materials |
All other fields |
| Sub-skill agents | Their own stage_output (via submit_output()) |
Any other field |
Dialogue log references (v3.3.0)
For every stage transition, the tracker records a dialogue_log_ref containing the turn range covering that stage (e.g. turns #47..#91). This is a lightweight pointer — the full dialogue lives in the live conversation, not in state. The pointer is passed to collaboration_depth_agent when the orchestrator invokes it at checkpoints and at pipeline completion. Turn-range entries are immutable once a stage closes.
collaboration_depth_history[]
Append-only list. Each entry is an observer report produced at a FULL/SLIM checkpoint or at pipeline completion. Entries never gate state transitions — they are stored for the final Process Record's "Collaboration Depth Trajectory" chapter only. The tracker must reject any write request that attempts to turn observer output into a blocking condition.
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 · 519 lines · 17 tokens per session scan A 062361fd178f
state_tracker_agent is an agent published in the GitHub repository LUNARTECH-X/superpowers (16 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 4,749 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-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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.