Borrowing it
Nothing to install: this file belongs to tacoda/keystone. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tacoda/keystone/main/.claude/agents/keystone-tracker-card-fetcher.mdgit clone --depth 1 https://github.com/tacoda/keystoneWrote 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/tacoda/keystone/keystone-tracker-card-fetcher)<a href="https://agentmods.dev/agents/tacoda/keystone/keystone-tracker-card-fetcher"><img src="https://agentmods.dev/badge/agents/tacoda/keystone/keystone-tracker-card-fetcher/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/tacoda/keystone/keystone-tracker-card-fetcher"><img src="https://agentmods.dev/badge/agents/tacoda/keystone/keystone-tracker-card-fetcher.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.00040 | $0.00249 |
| Opus 5 | $0.00020 | $0.00125 |
| Sonnet 5 | $0.00008 | $0.00050 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
keystone-tracker-card-fetcher 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 5d 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
94% identical to tracker-card-fetcher — 7 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.
What it actually says
Sensor: tracker-card-fetcher
Fetches a tracker card from Jira / Linear / GitHub Issues / Asana via whatever tracker integration the agent has (MCP server, CLI, policy), if one is referenced.
- Trigger — spec (when an ID or URL is provided), occasionally learn and review to surface card metadata in artifacts.
- Inputs — a card identifier (e.g.,
PROJ-123, a Linear URL, a GitHub Issue URL); the corresponding tracker integration. - Exit condition — card fetched, or "card not reachable" message produced if the integration is offline or the user lacks access.
- Output — title, description, acceptance criteria (if present), labels, links. The agent never edits the card unless the user explicitly asks.
- State writes — none. Card metadata lands in
docs/specs/<file>.mdinstead.
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.
- 5d ago First seen · 17 lines · 40 tokens per session scan A c9f2715b6f21
keystone-tracker-card-fetcher is an agent published in the GitHub repository tacoda/keystone (44 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 249 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to tracker-card-fetcher, differing in 7 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…