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/shrekshrek/project-workflow/feature-archivenpx skills add shrekshrek/project-workflow --skill feature-archivegit clone --depth 1 https://github.com/shrekshrek/project-workflowWrote 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/shrekshrek/project-workflow/feature-archive)<a href="https://agentmods.dev/skills/shrekshrek/project-workflow/feature-archive"><img src="https://agentmods.dev/badge/skills/shrekshrek/project-workflow/feature-archive.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.00025 | $0.00263 |
| Opus 5 | $0.00013 | $0.00131 |
| Sonnet 5 | $0.00005 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
feature-archive 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.
What it actually says
Feature Archive
Match the user's language and preserve file language. Read ${CLAUDE_PLUGIN_ROOT}/docs/actions/feature-archive.md completely before acting; it owns eligibility, lifecycle rules, and outputs.
Claude execution details:
- Parse
$ARGUMENTSas a feature slug/number/path or empty sweep mode using the shared runtime conventions. - Apply the canonical eligibility, freshness, and current-truth validation before mutation. Use Claude's native question flow when the action requires a user decision.
- Create a new current-truth document only from
${CLAUDE_PLUGIN_ROOT}/template/docs/specs/_template/domain.mdwhen the canonical action requires one. - Move approved directories with an ordinary filesystem rename, then run
node "${CLAUDE_PLUGIN_ROOT}/scripts/relocate-markdown-links.cjs" <old-dir> <new-dir>. If relocation fails, move the directory back before stopping; apply lifecycle/current-truth edits only after successful relocation. - Do not modify implementation code, delete history, or commit.
Report archived features, current-truth updates, superseded artifacts, ADR follow-ups, and unresolved items.
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 · 20 lines · 25 tokens per session scan A aeb69cdb3ca4
feature-archive is a skill published in the GitHub repository shrekshrek/project-workflow (2 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 263 once invoked, about $0.0001 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
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
unharness
Safely leave Citadel using the active adoption receipt. Produces a no-write, reviewable plan, preserves a portable archive, removes only exact owned material, and reports modified or externally registered surfaces as retained or unknown. Legacy installs must be imported before exact leave is claimed.
orient
Orient a spec-driven jig/servo/shaper repository with a read-only, project-wide briefing: start from the workflow.py orient headline, then survey open pull requests and unmerged work, Proposed ADRs, DEFERRED triggers, refinement items, release plans, the inbox, and the bug board; render one readable headline, titled…
process-backlog
Internal crew primitive, dispatched by /crew:run — do not invoke directly or select it for a user request; route backlog/catch-up requests to /crew:run, which decides the full workflow. (Function: find and advance stalled issues/PRs or ledger tasks, bounded; never merges.).
requirements
This skill should be used when the user asks to "write requirements", "create user stories", "define acceptance criteria", "decompose a feature", "analyze an issue", "write a PRD", "create user stories", "acceptance criteria", "roadmap", "feature spec", or discusses "INVEST" criteria, "ambiguity", or "story…