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/Arch1eSUN/ArcgenticWrote 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/arch1esun/arcgentic/ref-tracker)<a href="https://agentmods.dev/agents/arch1esun/arcgentic/ref-tracker"><img src="https://agentmods.dev/badge/agents/arch1esun/arcgentic/ref-tracker/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/arch1esun/arcgentic/ref-tracker"><img src="https://agentmods.dev/badge/agents/arch1esun/arcgentic/ref-tracker.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.00024 | $0.00253 |
| Opus 5.5 | $0.00010 | $0.00101 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 42 lines · 24 tokens per session scan A 6467e3d02778
ref-tracker is an agent published in the GitHub repository Arch1eSUN/Arcgentic (285 stars, last pushed 23d ago), licensed MIT. It adds 24 tokens to every session and 253 once invoked, about $0.0001 per session on Opus 5.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
plan-sync
Synchronizes downstream task specs after implementation. Spawned by flow-next-work once per resolved wave. Do not invoke directly.
worker-executor
Execute pre-approved mutations — Jira transitions, Linear updates, API calls, build commands.
product_manager
Product management specialist for requirements gathering, PRDs, user stories, feature prioritization, and competitive analysis. Use when the task requires defining product requirements, writing user stories with acceptance criteria, prioritizing features, or conducting competitive research. For example: writing a PRD…
complete-task
Completes one named task from the current milestone's task list, invoked with that task's heading text as the prompt.
phase-executor
Executes plans with deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator.
plan
Create structured implementation plans. Produces master plan + phase files for non-trivial work (3+ phases, 5+ files). Use before multi-phase implementation.