Borrowing it
Nothing to install: this file belongs to nguyenvanphituoc/shapeup-sdlc-plugin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nguyenvanphituoc/shapeup-sdlc-plugin/main/CLAUDE.mdgit clone --depth 1 https://github.com/nguyenvanphituoc/shapeup-sdlc-pluginWrote 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/instructions/nguyenvanphituoc/shapeup-sdlc-plugin/claude-md)<a href="https://agentmods.dev/instructions/nguyenvanphituoc/shapeup-sdlc-plugin/claude-md"><img src="https://agentmods.dev/badge/instructions/nguyenvanphituoc/shapeup-sdlc-plugin/claude-md.svg" alt="Measured on agentmods" 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.00872 | $0.00872 |
| Opus 5 | $0.00436 | $0.00436 |
| Sonnet 5 | $0.00174 | $0.00174 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
shapeup-sdlc-plugin CLAUDE.md 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 7d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
@AGENTS.md
Above the rule: the shipped harness doc. Below: guidance for developing this repo.
What this repo is
A Claude Code plugin (shapeup-sdlc). AGENTS.md is a shipped product artifact —
bin/init.mjs splices its <!-- HARNESS_START -->…<!-- HARNESS_END --> block into
consumer projects. Editing it is a product change: speak in skills/commands/options,
never .mjs paths.
Commands
npm test— Tier-0 structural suite (tests/structural/); zero deps, no install step.claude plugin validate . --strict(and the same for./.claude-plugin/marketplace.json) — CI parity.claude --plugin-dir .— load the working copy without installing.npm run demo— regeneratesdocs/assets/demo-gate.svgby running the real gate hook; never hand-edit the SVG.
Rules that prevent breakage
- Zero dependencies is load-bearing: executable code is plain Node ESM (
.mjs),node:builtins only, no network calls anywhere. - Hooks fail open, never closed, unless the bad state is positively proven
(
hooks/sandbox-guard.mjsis the reference implementation). - A version bump touches both
package.jsonand.claude-plugin/plugin.json; release CI fails on mismatch. - A new worker skill takes 3 steps:
SKILL.md→ declare fields inskills/tech-lead/schemas/domain.schema.json→ teachharness compileandharness reduce ingest. Step 1 alone yields a skill the orchestrator can't dispatch. tools/is repo-only and never ships; what ships is thefilesallowlist inpackage.json.- Commit subjects:
type(scope): lowercase declarative.
Keeping the docs and the plugin honest
This repo is both a product and its own blueprint, and the two drift apart silently — a doc saying "11 workers" over a 10-member enum reads perfectly. Two standing rules:
- Derive facts from artifacts, never from prose. Enums come from
skills/tech-lead/schemas/domain.schema.json, counts from the filesystem, and hook behavior from executing the hook against a fixture. A doc, a glossary and a screenshot can all agree with each other and all be wrong; reading any one of them just confirms the others. - Nothing in the shipped set may reference something the user did not receive. No benchmark
results, internal defect IDs (
HD-00x), migration stage names, audit codenames, or paths intodocs/,tests/,tools/,evals/. Keep the operative rationale, drop the evidence: a comment should explain why the code is shaped that way without citing an artifact the reader cannot open.
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.
- 7d ago First seen · 65 lines · 872 tokens per session scan A b92246486e55
shapeup-sdlc-plugin CLAUDE.md is an instructions file published in the GitHub repository nguyenvanphituoc/shapeup-sdlc-plugin (2 stars, last pushed 3d ago), licensed MIT. It adds 872 tokens to every session, about $0.0044 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.