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/volomydyr/design-engineer-plugin/dev-status-trackingnpx skills add volomydyr/design-engineer-plugin --skill dev-status-trackinggit clone --depth 1 https://github.com/volomydyr/design-engineer-pluginWrote 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/volomydyr/design-engineer-plugin/dev-status-tracking)<a href="https://agentmods.dev/skills/volomydyr/design-engineer-plugin/dev-status-tracking"><img src="https://agentmods.dev/badge/skills/volomydyr/design-engineer-plugin/dev-status-tracking.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.00035 | $0.01748 |
| Opus 5 | $0.00017 | $0.00874 |
| Sonnet 5 | $0.00007 | $0.00350 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade A, and why
dev-status-tracking 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 4d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Management
Why This Matters
When you work on something complex with AI, it forgets things. Every conversation has a token limit (~200,000 tokens), and when you hit it, earlier parts get compressed or lost. AI might forget components already built, decisions already made, and approaches that did not work.
The solution is simple: keep a status file for AI to read at the start of every development task. Sub-agents also help by running heavy work in separate chats with separate token limits, preserving the main conversation's budget.
Interaction Method
If AskUserQuestion is available, use it for all prompts below.
If not, present each question as a numbered list and wait for a reply before proceeding. For multiSelect questions, accept comma-separated numbers (e.g. 1, 3). Never skip or auto-answer without explicit user consent.
Step 0: Before starting
-
Announce your execution plan: Before doing anything, state what you will do in this activity: "Here's what I'm going to do: 1) set up a development status file for your project, 2) configure automatic update rules in CLAUDE.md, 3) implement the one-activity-per-chat pattern for context preservation, 4) share context survival strategies for long-running projects." This is a commitment device – harder to skip steps you just announced.
-
Conditional teaching: Ask the user if they are familiar with context management in AI-assisted development – why AI forgets things and how a status file helps. If yes, give a one-sentence refresher. If no, explain it in simple terms: every AI conversation has a memory limit, and when you hit it, earlier context gets compressed or lost – a status file is a persistent document AI reads at the start of every task so it knows what's been built, what's in progress, and what to avoid.
Required: ALWAYS ask the question, ALWAYS give the refresher when the user says yes. Never skip this step because the user "is a designer" or "already demonstrated familiarity earlier." Users want a memory refresh on every activity, including ones they know. Phrases like "I'll skip the explainer (you're a designer)" are forbidden — they signal the model has decided ON BEHALF OF the user that a refresher isn't needed. The user, not the model, decides what's redundant. The refresher takes one sentence; the cost is trivial; the value to a tired user mid-session is high.
What ships with it
3 files 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.
- 4d ago First seen · 140 lines · 35 tokens per session scan A 838c56269340
dev-status-tracking is a skill published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,748 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-30.
Other skills, from other repositories
retrieval-practice-generator
Generate low-stakes retrieval-practice questions with grounded answer notes and implementation guidance. Use for quiz starters, revision activities, delayed recall, misconception checks, or adapting recall difficulty.
generating-mod-envs
Generates and reviews mod learning env JSON files for Letta Code local mods. Use when asked to teach, learn, or optimize a mod behavior; create, draft, validate, improve, or explain envs for /mods learn --env; or design evaluation scenarios, memory fixtures, requiredResultMarkers, requiredTraceMarkers, negative…
aws-secrets-manager
Secret safety for AWS Secrets Manager, secret management, credentials, API keys, tokens, and passwords. Prevents AI agents from directly fetching secret values and teaches runtime dynamic references with asm-exec so plaintext never enters the LLM context window.
ai-memory-learning-maintenance
Use this skill for any ai-memory knowledge-base maintenance request: consolidating observations, reviewing session lessons, proposing durable learnings, auditing or linting the wiki, finding contradictions, pruning stale memory, or running auto-improvement. Trigger by semantic intent rather than exact wording.
self-improve-with-tinyfish
Enables Hermes to create new reusable skills for itself by researching live web sources with TinyFish Search and Fetch, analyzing source coverage, writing SKILL.md files, and installing them into Hermes memory. Use when the user asks Hermes to learn, teach itself, upgrade itself, or save a reusable capability.
cao-learning
Report task outcomes and distill lessons so the team improves across runs — reportoutcome after each unit of work, retrospector handoffs at natural boundaries, and applying injected lessons. Use in workflows that run repeatedly over similar work items. Requires memory.learningenabled; degrade silently when the tools…