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/hamzabellouch/agent-skills/state_tracker_agentgit clone --depth 1 https://github.com/hamzabellouch/agent-skillsWrote 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/hamzabellouch/agent-skills/state_tracker_agent)<a href="https://agentmods.dev/agents/hamzabellouch/agent-skills/state_tracker_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/state_tracker_agent.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.1 | $0.00017 | $0.04884 |
| Opus 5 | $0.00009 | $0.02442 |
| Sonnet 5 | $0.00003 | $0.00977 |
| Haiku 4.5 | $0.00002 | $0.00488 |
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.
This is a copy
89% identical to state-tracker-agent — 116 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.
How it starts
The opening of the file, as written. The whole thing — 507 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 during Stage 6 record compilation (the whole-pipeline pass). 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 during Stage 6 record compilation (the whole-pipeline pass). 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 · 507 lines · 17 tokens per session scan A 6528349959ae
state_tracker_agent is an agent published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 4,884 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to state-tracker-agent, differing in 116 lines, and is treated as a copy.
Other agents, from other repositories
phase-researcher
You are now operating as the learnship phase researcher. You answer "What do I need to know to PLAN this phase well?" and produce a single RESEARCH.md that the planner consumes.
planner
You are now operating as the learnship planner. Your job is to create executable PLAN.md files that decompose a phase goal into atomic, independently verifiable tasks with wave-based dependency ordering.
research-synthesizer
You are now operating as the learnship research synthesizer. You read the outputs from 4 parallel researcher agents (or 4 sequentially-written research files) and synthesize them into a cohesive SUMMARY.md.
code-reviewer
Expert code reviewer. Proactively reviews code changes for quality, security, and best practices. Use after implementing features or fixing bugs to ensure code quality.
security-auditor
专注于漏洞检测、威胁建模和安全编码实践的 Security engineer。用于 security-focused code review、threat analysis 或 hardening recommendations。.
security-auditor
Security auditor focused on OWASP Top 10 compliance and vulnerability prevention.