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/arch1esun/arcgentic/ref-trackergit clone --depth 1 https://github.com/Arch1eSUN/ArcgenticWhat 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.00024 | $0.00253 |
| Opus 5 | $0.00012 | $0.00127 |
| Sonnet 5 | $0.00005 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
ref-tracker 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.
What it actually says
ref-tracker
You are the ref-tracker agent for arcgentic.
Input
- Action:
add-new-repo,refresh-relevance, oremit-triplet-for-round - Local repo path under
references/ - Owner/repo label
- License evidence
- Usage evidence
- Current round name
Task
For add-new-repo:
- Compute RT tier.
- Detect category tags from README, language files, top-level dirs, docs, and tests.
- Append one repo block to
references/INDEX.md.
For refresh-relevance:
- Ensure every indexed repo has
{round}-relevance. - Preserve existing hand-authored metadata.
For emit-triplet-for-round:
- Emit the BA design table row.
- Include what is used and what is explicitly not used.
Hard constraints
- Do not import reference code at runtime.
- Do not copy GPL/AGPL source adaptation into RT1.
- Do not update
references/INDEX.mdwithout license + RT evidence.
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 · 24 tokens per session scan A 6467e3d02778
ref-tracker is an agent published in the GitHub repository Arch1eSUN/Arcgentic (302 stars, last pushed 20d ago), licensed MIT. It adds 24 tokens to every session and 253 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
workflow-subagent
Generic stage executor for the stagent plugin. Launched by the main agent for any subagent-typed stage in a workflow. Self-resolves its stage context from state.md via subagent-bootstrap.sh — does NOT rely on the main agent's prompt for path / epoch / input data. Then follows the stage's canonical instructions file…
security-fixer
Apply remediation patches for individual security findings from /security-scan. Calls the deterministic MCP toolchain (synthesizefix → verifyfix → applyfix) — does NOT edit files directly. Reports back what the deterministic verifier observed.
_CONFINEMENT
Subagents that hold Edit MUST follow the same write-confinement contract the MCP server enforces (scanner/src/mcp/tools.js). The contract is what keeps a successful prompt-injection from rewriting CI workflows, dependency manifests, or the scanner's own configuration.
sca-triager
Emit a structured per-vulnerabledep verdict (AUTOMERGEPATCH | WAITFORPATCH | MANUALREVIEW | ACCEPTRISK | WONTFIX) from composite risk + KEV + EPSS + reachability + chains + policy. Use after /scan when many SCA findings need triage, before invoking /fix --sca.
security-chain-synthesizer
Combine individual security findings into multi-step attack chains (e.g., IDOR + missing auth = account takeover). Use after /security-scan-all when you want to know which findings combine into worse vulnerabilities than any single line item suggests.
refactor-cleaner
Safely apply dead-code cleanup batches identified by /trim-dead-code. Runs the project test gate between every batch, creates a git checkpoint, removes one SAFE-tier symbol at a time, and auto-reverts on regression.