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 skills/flurdy/agent-skills/tracking-sweepnpx skills add flurdy/agent-skills --skill tracking-sweepgit 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/skills/flurdy/agent-skills/tracking-sweep)<a href="https://agentmods.dev/skills/flurdy/agent-skills/tracking-sweep"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/tracking-sweep.svg" alt="Measured on agentmods" 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.00085 | $0.03808 |
| Opus 5 | $0.00043 | $0.01904 |
| Sonnet 5 | $0.00017 | $0.00762 |
| Haiku 4.5 | $0.00009 | $0.00381 |
Grade A, and why
tracking-sweep 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 6d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tracking Sweep — Portfolio Drift Reconciliation
Cross-reference your assigned Jira tickets, beads, and GitHub PRs to flag drift across the portfolio. Read-only. Recommendations only — never auto-posts comments, never moves Jira status, never closes beads.
Relationship to other tools
/landscapeis passive display: lists everything in three sections, side-by-side. Doesn't cross-reference.tracking-auditor(agent) is per-branch depth: "does THIS branch's diff match its ticket?" Used as a PR-boundary gate./tracking-sweep(this skill) is portfolio breadth: "across everything in flight, where's the drift?" Used ad-hoc.
If a single branch looks suspicious during the sweep, recommend invoking tracking-auditor for that branch — don't replicate its logic.
Usage
/tracking-sweep # Full sweep
/tracking-sweep quick # Skip stale-beads + PR-detail fetches (faster)
Output
A drift report. Items that match across all three systems are NOT listed — only deviations. If there's no drift, the report is short. That's the point.
Procedure
Run sections 1–3 in parallel (independent data fetches). Sections 4+ are sequential cross-referencing.
1. Fetch Jira tickets
Tickets assigned to current user, not Done. Include the sprint custom field (customfield_10020) — the table both displays it and orders by it:
mcp__jira__jira_get
path: /rest/api/3/search/jql
queryParams:
jql: assignee = currentUser() AND statusCategory != Done ORDER BY updated DESC
fields: summary,status,issuetype,priority,updated,parent,resolution,customfield_10020
maxResults: 50
jq: issues[*].{key: key, summary: fields.summary, status: fields.status.name, type: fields.issuetype.name, priority: fields.priority.name, updated: fields.updated, parent: fields.parent.key, sprint: fields.customfield_10020}
The sprint field is an array of sprint objects. For each ticket extract the active sprint's name (first entry where state == "active"), else the most recent. Empty/null → — (no sprint — usually backlog).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 263 lines · 85 tokens per session scan A 9d54e228370d
tracking-sweep is a skill published in the GitHub repository flurdy/agent-skills (8 stars, last pushed 7d ago), licensed MIT. It adds 85 tokens to every session and 3,808 once invoked, about $0.0004 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.