agentmods.dev

purge-initiative-artifacts-meta

purge-initiative-artifacts-meta is a skill for Claude Code from drivestream-lab/prayog-skills. It costs 92 tokens per session (1,223 once invoked), scanned A, original, MIT.

A controlled cleanup workflow for deleting two temporary project-management reports for one initiative from a metadata repository.

In plain words
What is it for?
Removing an initiative’s validation report and resolution report after they are no longer needed, while leaving the repository history intact.
Why use it?
It limits deletion to named report files and protects durable documents such as the product requirements document and impact map.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

not rated 2repo 1mo ago A scan 92 tokens original MIT

Good fit Removing an initiative’s validation report and resolution report after they are no longer needed, while leaving the repository history intact.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/drivestream-lab/prayog-skills/purge-initiative-artifacts-meta
View source ↗ drivestream-lab/prayog-skills
Install

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.

Any agent
npx skills add drivestream-lab/prayog-skills --skill purge-initiative-artifacts-meta
Clone the repo
git clone --depth 1 https://github.com/drivestream-lab/prayog-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for purge-initiative-artifacts-meta

README.md
[![agentmods](https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/purge-initiative-artifacts-meta/github.svg)](https://agentmods.dev/skills/drivestream-lab/prayog-skills/purge-initiative-artifacts-meta)
Your own site
<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.

agentmods 80×15 button for purge-initiative-artifacts-meta

Your own site · 80×15
<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>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,223 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00092 $0.01223
Opus 5.5 $0.00037 $0.00489
Sonnet 5.5 $0.00018 $0.00245
Haiku 4.5 $0.00009 $0.00122

Measured 2mo ago against content hash 42b0037dea6f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

skills/requirements/purge-initiative-artifacts-meta/SKILL.md · 107 lines

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

  1. Resolve layout from .harness/profile.yaml or references/layout-defaults.md.
  2. Require initiative id INIT-*. Scope deletes to that initiative only.
  3. Delete only when present:
    • {reports_dir}/Validation-Report-{INIT}.md
    • {reports_dir}/Resolution-{INIT}.md
  4. Refuse (never delete): prd/INIT-*.md for this initiative; {reports_dir}/Impact-Map-{INIT}.md; service catalog; governance.
  5. Idempotent: missing allowlisted files → ok. Empty delete set → still pass with rationale in handoff signals.
  6. Workspace is the meta checkout (Gateflow binds meta root; human runs in meta clone). Fill handoff.forge for commit_workspace when pin requires it. When pin next is an open_draft_pr external-action, fill title and forge requires without creating a reports/ purge file (see output template).
  7. No Gateflow authorize-before-delete. No merge. Never apply *-lgtm.
  8. 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 in signals. Chat may repeat the same summary.
  9. Dual-walker parity with human /purge-initiative-artifacts-meta.

Inputs

  1. Initiative id — (REQUIRED)
  2. Workspace — meta repo root (REQUIRED)
  3. Layout — profile or layout-defaults
  4. Handoff baton — when handoff_path bound

Read the full file on GitHub · 107 lines

Files

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.

Changes

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.

  1. 2mo ago First seen · 107 lines · 92 tokens per session scan A 42b0037dea6f

Subscribe to this mod's changes

purge-initiative-artifacts-meta is a skill published in the GitHub repository drivestream-lab/prayog-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 1,223 once invoked, about $0.0004 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.

Project management
Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens