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-metagit 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-meta)<a href="https://agentmods.dev/skills/drivestream-lab/prayog-skills/purge-initiative-artifacts-meta"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/purge-initiative-artifacts-meta/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-meta"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/purge-initiative-artifacts-meta.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.00092 | $0.01223 |
| Opus 5 | $0.00046 | $0.00611 |
| Sonnet 5 | $0.00018 | $0.00245 |
| Haiku 4.5 | $0.00009 | $0.00122 |
Grade A, and why
purge-initiative-artifacts-meta 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 12d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purge initiative artifacts (meta)
Lane: PM / meta repo (profile: meta-pm).
Delete PURGE-set files under the meta repo for one initiative. Do not delete durable KEEP roots. Git history remains the archive.
This skill is independent of app/engineering purge. Do not require, invoke,
or document /purge-initiative-artifacts-app as a prerequisite or prior 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 when present:
{reports_dir}/Validation-Report-{INIT}.md{reports_dir}/Resolution-{INIT}.md
- Refuse (never delete):
prd/INIT-*.mdfor this initiative;{reports_dir}/Impact-Map-{INIT}.md; service catalog; governance. - Idempotent: missing allowlisted files → ok. Empty delete set → still
passwith rationale in handoff signals. - Workspace is the meta checkout (Gateflow binds meta root; human runs in
meta clone). Fill
handoff.forgeforcommit_workspacewhen pin requires it. When pin next is anopen_draft_prexternal-action, fill title and forge requires without creating a reports/ purge 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 parity with human
/purge-initiative-artifacts-meta.
Inputs
- Initiative id — (REQUIRED)
- Workspace — meta repo root (REQUIRED)
- Layout — profile or layout-defaults
- Handoff baton — when
handoff_pathbound
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.
- 12d ago First seen · 107 lines · 92 tokens per session scan A 42b0037dea6f
purge-initiative-artifacts-meta is a skill published in the GitHub repository drivestream-lab/prayog-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 92 tokens to every session and 1,223 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.