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 skills add drivestream-lab/prayog-skills --skill purge-initiative-artifacts-appgit clone --depth 1 https://github.com/drivestream-lab/prayog-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/drivestream-lab/prayog-skills/purge-initiative-artifacts-app)<a href="https://agentmods.dev/skills/drivestream-lab/prayog-skills/purge-initiative-artifacts-app"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/purge-initiative-artifacts-app/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/drivestream-lab/prayog-skills/purge-initiative-artifacts-app"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/purge-initiative-artifacts-app.svg" alt="Reviewed on agentmods" width="80" 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.00106 | $0.01502 |
| Opus 5 | $0.00053 | $0.00751 |
| Sonnet 5 | $0.00021 | $0.00300 |
| Haiku 4.5 | $0.00011 | $0.00150 |
Grade A, and why
purge-initiative-artifacts-app 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purge initiative artifacts (app)
Lane: engineering / app repo (profile: development).
Delete PURGE-set files under the app repo for one initiative. Do not delete durable KEEP roots. Git history remains the archive.
This skill is independent of meta/PM purge. Do not require, invoke, or
document /purge-initiative-artifacts-meta as a prerequisite or next step —
orchestration order lives only in pinned workflow.yaml.
Normative allowlist / refuse:
prayog-skills/references/artifact-write-contract.md.
NON-NEGOTIABLE
- Resolve layout from
.harness/profile.yamlor references/layout-defaults.md. - Require initiative id
INIT-*. Scope deletes to that initiative only. - Delete only the app PURGE allowlist when present:
{reports_dir}/Initiative-Feasibility-Report-{INIT}.md{reports_dir}/Technical-Review-{INIT}.md{reports_dir}/Implementation-Plan-{INIT}.md{reports_dir}/Pre-Implement-{INIT}-W*.md{reports_dir}/Wave-Execution-{INIT}-W*.md{reports_dir}/Live-Verify-{INIT}-W*.md{reports_dir}/Ground-Report-*-W*.mdfor this initiative/spec{reports_dir}/Learning-Extract-{INIT}-W*.md{adr_dir}/adr-*-*.mdthat are still Draft (not Accepted)
- Refuse (never delete):
{product_spec_dir}/INIT-*.mdfor this initiative; Accepted ADRs; anything undersource_roots,unit_tests_dir,live_verify_dirscripts,fixtures_dirpacks;.harness/; product source;{as_built_dir}/implementation-status.md(index) and{as_built_dir}/Implementation-Status-{INIT}.md(this initiative's detail) — bothKEEP, never on the PURGE allowlist. - Idempotent: missing allowlisted files → ok. Empty delete set → still
passwith rationale in handoff signals. - Work on the initiative-closure head cut from integration (
develop) when bound; do not invent a branch. Fillhandoff.forgeforcommit_workspacewhen pin requires commit. When pin next is anopen_draft_prexternal-action (eng closure PR), fill title/body from signals without creating a reports/ file (see output template). - No Gateflow authorize-before-delete. No merge. Never apply
*-lgtm. - No report file. Do not write
Purge-*.md(or any new artifact) under{reports_dir}. Goal achieved = handoff envelope (+ baton when bound) with delete/refuse lists insignals. Chat may repeat the same summary. - Dual-walker: same procedure for human
/purge-initiative-artifacts-appand Gateflow orch.
What ships with it
7 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 Changed · +1 lines 2e1ea398e4fe
- 12d ago First seen · 121 lines · 106 tokens per session scan A 63fc00d6a609
purge-initiative-artifacts-app is a skill published in the GitHub repository drivestream-lab/prayog-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 106 tokens to every session and 1,502 once invoked, about $0.0005 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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…