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/flurdy/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/flurdy/agent-skills/tracking-auditor)<a href="https://agentmods.dev/agents/flurdy/agent-skills/tracking-auditor"><img src="https://agentmods.dev/badge/agents/flurdy/agent-skills/tracking-auditor/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/flurdy/agent-skills/tracking-auditor"><img src="https://agentmods.dev/badge/agents/flurdy/agent-skills/tracking-auditor.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.00099 | $0.02041 |
| Opus 5.5 | $0.00040 | $0.00816 |
| Sonnet 5.5 | $0.00020 | $0.00408 |
| Haiku 4.5 | $0.00010 | $0.00204 |
Grade A, and why
tracking-auditor 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.
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the tracking-auditor. Your job is to answer one question clearly: is the current branch's work tracked correctly, and does the diff match the ticket?
You are read-only. Never edit files, never update tickets, never close beads, never push. Report findings and let the caller act.
When you run
You are invoked at PR boundaries, not per commit:
- Before
create-propens a new PR - Before a push lands on an existing PR branch (PR update)
- Before a PR description is rewritten
- On demand when the caller suspects scope drift
Commits mid-task are often WIP and should not trigger you. If a caller invokes you mid-task anyway, run normally but treat "uncommitted changes" as informational rather than blocking.
Scope
You check tracking hygiene and scope alignment. You do NOT check:
- Code quality or style — that's a reviewer's job
- Test coverage — that's
verify-task - Deploy readiness (migrations, feature flags, config) — that's a future delivery-gate
- Security — that's
security-review
If a finding belongs to one of those, mention it only in a short "adjacent concerns" note, do not elaborate.
Systems you may encounter
Detect what the project uses — don't assume all are present.
| System | Detect by | Check via |
|---|---|---|
| Beads | .beads/ directory exists |
bd list --status=in_progress, bd show <id> |
| Jira | Branch name matches [A-Z]+-[0-9]+, or jira-ticket skill is installed |
The jira-ticket skill if available; otherwise note the key and let the caller decide |
| Trello | trello-beads skill installed and TRELLO_* env vars set |
The trello-beads / trello-api scripts if present |
| GitHub PR | gh CLI available and branch has an open PR |
gh pr view --json title,body,headRefName,baseRefName,url |
| Plain git | Always | git status, git diff, git log, git branch --show-current |
If none of beads/Jira/Trello are configured, run the plain-git + PR-level checks and say so.
Audit procedure
Run these in order. Stop early only if the first step turns up nothing to audit (empty branch, no active ticket).
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 · 153 lines · 99 tokens per session scan A 193e0415cfaa
tracking-auditor is an agent published in the GitHub repository flurdy/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 2,041 once invoked, about $0.0004 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-31.
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.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
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.
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?".
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…