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 zeeshanhanif/agentic-sdlc-kit --skill pipeline-verifygit clone --depth 1 https://github.com/zeeshanhanif/agentic-sdlc-kitWrote 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/zeeshanhanif/agentic-sdlc-kit/pipeline-verify)<a href="https://agentmods.dev/skills/zeeshanhanif/agentic-sdlc-kit/pipeline-verify"><img src="https://agentmods.dev/badge/skills/zeeshanhanif/agentic-sdlc-kit/pipeline-verify/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/zeeshanhanif/agentic-sdlc-kit/pipeline-verify"><img src="https://agentmods.dev/badge/skills/zeeshanhanif/agentic-sdlc-kit/pipeline-verify.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.00207 | $0.01447 |
| Opus 5 | $0.00103 | $0.00724 |
| Sonnet 5 | $0.00041 | $0.00289 |
| Haiku 4.5 | $0.00021 | $0.00145 |
Grade A, and why
pipeline-verify 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Verify
The second tier of the pipeline's verification design. Tier 1 is built into every stage skill — each verifies its own contract at delivery. Tier 2 is this skill: the seams between documents that no single stage can see — a citation written correctly by one skill against a document another skill later amended, an FR that every stage individually handled but no stage ever covered, a manifest locator that rotted when a heading moved.
Three principles govern it:
- Mechanical only. Every check here is decidable by reading and computing — IDs resolve or don't, sets cover or don't, values match or don't. Judgment quality (is the architecture good, are the tests meaningful) belongs to the stage skills and their auditors; a check that needs taste doesn't belong in this skill.
- Read-only, derived-output-only. This skill writes nothing into any pipeline artifact — no RTM column, no document fix, no "helpful" correction. Its single output is the report, an explicitly derived view: safe to overwrite, safe to delete, regenerable at any time. Findings route to their owning skills; fixing is theirs.
- Fresh eyes, actual commands. Run it cold — it needs no session context, only the repo. And extract mechanically: grep/parse the IDs, diff the sets, resolve the locators with real commands — never eyeball a 700-row matrix. The checks are specified so a script could run them; run them like a script would.
When to run
After any system-level phase completes (catch seam breaks while the phase's author-skill session is still warm); before handing the loop to the orchestrator for a long run; after amendment chains (the highest-risk moment for dangling references); periodically on mature projects. Full sweep by default; targeted scope on request ("check the RTM", "check FEAT-007's seams").
Inputs
Everything, read-only: docs/srs.md, use-cases.md, rtm.md,
architecture.md, ux-foundations.md, design.md, tokens.json,
implementation-plan.md, design-manifest.json, docs/features/**,
docs/defects.md, scaffold/deploy notes where present. Absent documents
scope their checks out (source-gating applies to verification too — a
missing use-cases.md means UC checks are skipped and reported as skipped,
never failed).
What ships with it
2 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.
- 8d ago First seen · 127 lines · 207 tokens per session scan A 7e7c6b9d973e
pipeline-verify is a skill published in the GitHub repository zeeshanhanif/agentic-sdlc-kit (5 stars, last pushed 13d ago), licensed Apache-2.0. It adds 207 tokens to every session and 1,447 once invoked, about $0.0010 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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…