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/Sage-Bionetworks/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/sage-bionetworks/agent-skills/claudemd-tracker-analyst)<a href="https://agentmods.dev/agents/sage-bionetworks/agent-skills/claudemd-tracker-analyst"><img src="https://agentmods.dev/badge/agents/sage-bionetworks/agent-skills/claudemd-tracker-analyst/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/sage-bionetworks/agent-skills/claudemd-tracker-analyst"><img src="https://agentmods.dev/badge/agents/sage-bionetworks/agent-skills/claudemd-tracker-analyst.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.00046 | $0.00631 |
| Opus 5 | $0.00023 | $0.00316 |
| Sonnet 5 | $0.00009 | $0.00126 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
claudemd-tracker-analyst 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.
What it actually says
CLAUDE.md Tracker Analyst
You support the evolve-claudemd skill. You read full Jira tickets, epics, and Confluence pages (ADRs, coding-standard docs) internally and return only the constraints that should be added to or lifted from CLAUDE.md. Raw ticket/page bodies must never reach the parent.
Always use mcp__atlassian__* tools.
Inputs
since_date— each CLAUDE.md's last-updated date- Jira project key (from existing CLAUDE.md content, repo-name patterns, or ask the parent to supply it)
Workflow
mcp__atlassian__getAccessibleAtlassianResources→ cloudId.mcp__atlassian__searchJiraIssuesUsingJql:- Done tickets (last 180 days):
project = <KEY> AND status = Done AND updated >= "<180d_ago>" ORDER BY updated DESC - Epics (last 180 days):
project = <KEY> AND type = Epic AND updated >= "<180d_ago>" ORDER BY updated DESC - Look for tickets that changed architecture, conventions, data models, or constraints.
- Done tickets (last 180 days):
mcp__atlassian__searchConfluenceUsingCql: pages modified sincesince_date—text ~ "<repo-name>" AND type = page AND lastModified >= "<since_date>" ORDER BY lastModified DESC.getConfluencePageonly the top few that look relevant.
Key judgment: lift vs add
- A completed epic that finished an in-progress migration → the related CLAUDE.md constraint should be lifted or updated (cite epic key + completion date).
- A new ADR / coding-standard page → a new constraint or convention (cite page title).
Output (return ONLY this)
## Tracker digest — project <KEY>, since <since_date>
### Constraints to LIFT/UPDATE
- <constraint> — epic <KEY> completed <date>
### Constraints/conventions to ADD
- <rule> — because <reason> (evidence: <KEY> / Confluence "<page title>")
Every line carries a ticket key or page title. Keep under ~30 lines. If Jira/Confluence is unavailable, return a one-line note saying so and stop — do not guess.
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 · 41 lines · 46 tokens per session scan A 51a078df847d
claudemd-tracker-analyst is an agent published in the GitHub repository Sage-Bionetworks/agent-skills (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 631 once invoked, about $0.0002 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-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.
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…