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.
git clone --depth 1 https://github.com/Masqiller/ARG-RESEARCHER-V4.1Wrote 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/masqiller/arg-researcher-v4.1/state_tracker_agent)<a href="https://agentmods.dev/agents/masqiller/arg-researcher-v4.1/state_tracker_agent"><img src="https://agentmods.dev/badge/agents/masqiller/arg-researcher-v4.1/state_tracker_agent/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/agents/masqiller/arg-researcher-v4.1/state_tracker_agent"><img src="https://agentmods.dev/badge/agents/masqiller/arg-researcher-v4.1/state_tracker_agent.svg" alt="Reviewed on agentmods" width="80" 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.04756 |
| Opus 5 | $0.00009 | $0.02378 |
| Sonnet 5 | $0.00003 | $0.00951 |
| Haiku 4.5 | $0.00002 | $0.00476 |
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 10d 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
92% identical to state-tracker-agent — 70 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 — 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 Dr. Pooja, 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.
- 10d ago First seen · 519 lines · 17 tokens per session scan A b87d866fda50
state_tracker_agent is an agent published in the GitHub repository Masqiller/ARG-RESEARCHER-V4.1 (6 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 4,756 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to state-tracker-agent, differing in 70 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…