Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentnpx agentmods add skills/matrixfounder/agentic-development/skill-archive-taskWrote 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/matrixfounder/agentic-development/skill-archive-task)<a href="https://agentmods.dev/skills/matrixfounder/agentic-development/skill-archive-task"><img src="https://agentmods.dev/badge/skills/matrixfounder/agentic-development/skill-archive-task/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/skills/matrixfounder/agentic-development/skill-archive-task"><img src="https://agentmods.dev/badge/skills/matrixfounder/agentic-development/skill-archive-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.06343 |
| Opus 5.5 | $0.00017 | $0.02537 |
| Sonnet 5.5 | $0.00008 | $0.01269 |
| Haiku 4.5 | $0.00004 | $0.00634 |
Grade A, and why
skill-archive-task 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 8d 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 — 452 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Archiving Protocol
This skill encapsulates the complete protocol for archiving docs/TASK.md to docs/tasks/
and docs/PLAN.md to docs/plans/ (in lockstep with TASK.md). Step 8 then re-targets the links
that the task wrote into the two slots.
When to Archive
Archive docs/TASK.md ONLY when:
- Starting a NEW task AND
docs/TASK.mdexists with DIFFERENT content - Completing a task (Orchestrator Completion stage)
DO NOT archive when:
- Refining/clarifying the CURRENT task (overwrite instead)
docs/TASK.mddoes not exist
[!IMPORTANT] PLAN.md rotates in lockstep with TASK.md. Whenever TASK.md is archived for a NEW task, the old
docs/PLAN.md(if present) is archived too — see "PLAN.md Archiving (Lockstep)" below. On task refinement, PLAN.md is overwritten in place, never archived.docs/ARCHITECTURE.mdis a LIVING document: this skill never moves or archives it. Step 8 may re-target the task's own slot links in it.
Decision Logic: New vs Refinement
IF user request implies a NEW SEPARATE feature/refactor:
→ Archive existing TASK.md, then create new
IF user request is a clarification/refinement of CURRENT task:
→ Overwrite TASK.md, do NOT archive
Indicators of NEW task:
- Different feature/component mentioned
- "Create new task for...", "Start working on..."
- Completed previous task
Indicators of REFINEMENT:
- "Clarify requirement X", "Add detail to..."
- Same feature context as current TASK.md
Protocol Steps
Step 1: Check Condition
IF NOT exists("docs/TASK.md"):
SKIP archiving → Create new TASK.md
Step 2: Extract Metadata
Read from current docs/TASK.md:
- Task ID from "0. Meta Information" section
- Slug from "0. Meta Information" section
- Base revision from the same section, as
{base_revision}: the commit at which the task started. Step 8 passes it as--since. Without one, readBase revisionfrom the header ofdocs/reviews/framework-audit-<ID>.md. Strip one pair of enclosing backticks; the rest must be 7–64 hexadecimal digits, andnone, no value or any other value means no base. Never use a base that the current run recorded.
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.
- 8d ago Changed · +69 lines · +11 tokens per session f71ff61a3a02
- 9d ago Changed · +18 lines 379c87cf9a77
- 1mo ago First seen · 365 lines · 31 tokens per session scan A 86e932df1d7a
skill-archive-task is a skill published in the GitHub repository MatrixFounder/Agentic-development (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 42 tokens to every session and 6,343 once invoked, about $0.0002 per session on Opus 5.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
08-debug
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
workflow
Perform any development work on the ambient-ui component. Full workflow instructions.
chimera-write-the-check-before-the-code
A criterion written after the implementation describes the implementation. Write the failing check first, watch it fail, then build.
Learn what defines effective BDD scenarios
Interactive guidance on writing complete, effective BDD scenarios for story-flow.
hatch3r-bug-fix
Step-by-step bug fix workflow. Diagnose root cause, implement minimal fix, write regression test. Use when fixing bugs, working on bug report issues, or when the user mentions a bug.
ap-policies
Attach a completion policy gate (shell check or judge-agent rubric) to a session or fan-in group so turn-end only passes when the gate is green, then optionally auto-commit pending human ack. Use when the user says "gate this session on tests passing", "attach a policy", "commit only if tests are green", "judge…