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/youngjaedev/my-claude-plugins/state-trackernpx skills add YoungjaeDev/my-claude-plugins --skill state-trackergit clone --depth 1 https://github.com/YoungjaeDev/my-claude-pluginsWrote 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/youngjaedev/my-claude-plugins/state-tracker)<a href="https://agentmods.dev/skills/youngjaedev/my-claude-plugins/state-tracker"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/state-tracker.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 | $0.00080 | $0.01283 |
| Opus 5 | $0.00040 | $0.00642 |
| Sonnet 5 | $0.00016 | $0.00257 |
| Haiku 4.5 | $0.00008 | $0.00128 |
Grade B, and why
state-tracker scanned grade B with 1 finding 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
2. `find .claude/spec -maxdepth 1 -name '*.md' -not -name '_template.md'`. How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
state-tracker
.claude/state/spec.json is a one-file aggregate of the project's spec/issue/PR work pipeline. It exists so an LLM (or human) can answer "what's currently in flight, and against which spec?" with a single Read — no find over .claude/spec/ plus per-file frontmatter parse.
Ships with the
devplugin; install via marketplace. Operates on the current repo's.claude/state/spec.json.
SSOT relationship
| Source | Authority | When it wins |
|---|---|---|
.claude/spec/*.md frontmatter (status:) |
SSOT | Always — the spec file is the truth |
.claude/state/spec.json |
aggregate cache | Faster lookup; if it conflicts with frontmatter, regenerate from frontmatter |
The cache is regeneratable any time via init (scan spec dir + frontmatter aggregate). Direct edits are allowed but rare — prefer the 4 ops below.
Schema (versioned JSON)
{
"schema": 1,
"updated_at": "<ISO 8601>",
"in_progress": [
{
"spec": ".claude/spec/<YYYY-MM-DD>-<slug>.md",
"section": "<spec internal anchor, optional>",
"linked": { "issue": <number or null>, "pr": <number or null> },
"description": "<spec 'Goal' first line, or user-provided one-liner>"
}
],
"completed": [
{
"spec": ".claude/spec/<YYYY-MM-DD>-<slug>.md",
"linked": { "issue": <number or null>, "pr": <number or null> },
"description": "<same as above>",
"completed_at": "<YYYY-MM-DD>",
"merge_sha": "<short SHA, 7 chars>"
}
]
}
Operations
read — print current state
- If
.claude/state/spec.jsondoes not exist → print empty state ({ "in_progress": [], "completed": [] }) and inform the user. Do NOT auto-create; ask if they wantinit. - Read and pretty-print. Highlight
in_progressfirst.
init — regenerate from spec frontmatter (one-shot)
- Confirm with user (
AskUserQuestion) — this overwrites the file. Default: cancel. find .claude/spec -maxdepth 1 -name '*.md' -not -name '_template.md'.- For each spec file, parse YAML frontmatter (best effort):
status: draft | in-progress | merged→ bucket selection## Goalfirst non-empty line →description- Optional
issue:/pr:keys →linked
- Write
.claude/state/spec.jsonwithschema: 1andupdated_at= now. - Print summary:
N in-progress, M completed.
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.
- today Changed a056f6f26538
- 5d ago First seen · 108 lines · 80 tokens per session scan B f63fdccd18a5
state-tracker is a skill published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 1,283 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…