Borrowing it
Nothing to install: this file belongs to codervisor/leanspec. 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/codervisor/leanspec/main/.agents/skills/leanspec-pr-lifecycle/SKILL.mdgit clone --depth 1 https://github.com/codervisor/leanspecWrote 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/codervisor/leanspec/leanspec-pr-lifecycle)<a href="https://agentmods.dev/skills/codervisor/leanspec/leanspec-pr-lifecycle"><img src="https://agentmods.dev/badge/skills/codervisor/leanspec/leanspec-pr-lifecycle/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/codervisor/leanspec/leanspec-pr-lifecycle"><img src="https://agentmods.dev/badge/skills/codervisor/leanspec/leanspec-pr-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 182 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Agent Snooping · line 185 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 188 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- low Excessive Agency · line 166 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00169 | $0.03129 |
| Opus 5.5 | $0.00068 | $0.01252 |
| Sonnet 5.5 | $0.00034 | $0.00626 |
| Haiku 4.5 | $0.00017 | $0.00313 |
Grade A, and why
leanspec-pr-lifecycle 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.
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
leanspec-pr-lifecycle
Everything that happens after git push on a lean-spec PR. Covers spec-issue linking, CI triage, review-comment discipline, webhook subscription, and the manual ticking of Plan items / CHANGELOG entries on merge.
This is lean-spec's analogue of onsager-pr-lifecycle / duhem-pr-lifecycle. The discipline is the same.
Tool discipline
- No
ghCLI for issue/PR manipulation, nohub, no direct GitHub API. Always usemcp__github__*. TheghCLI is fine for CI workflow inspection (gh run list,gh run view) — seeleanspec-development"CI/CD"; it's just not the tool for spec-label updates or PR body edits. - Scope is restricted to
codervisor/leanspecfor this skill. - Don't open PRs unless the user explicitly asks. Creating one is a one-way door in this project's workflow.
Spec-issue linking (mandatory)
Every PR must either:
- Link to a spec issue in its body via
Closes #N/Fixes #N/Resolves #N(slice complete) orPart of #N/Refs #N(scaffolding), OR - Carry the
triviallabel (typo, doc-only, one-line obvious fix).
If neither, the PR is out of process. Comment on the PR asking the author to add a spec link — creating one via issue-spec if none exists — or apply the trivial label.
Which keyword to use
GitHub closes issues on merge when the PR body contains one of: close, closes, closed, fix, fixes, fixed, resolve, resolves, resolved — followed by #N.
Pick the keyword based on what this PR actually delivers:
| PR delivers | Use |
|---|---|
| The acceptance test / vertical slice the spec asks for | Closes #N |
| A bug fix for a specific defect | Fixes #N |
| Scaffolding / one phase of a multi-phase spec | Part of #N |
| Related work that shouldn't close the spec | Refs #N |
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.
- 2mo ago First seen · 189 lines · 169 tokens per session scan A 993a99acaf9d
leanspec-pr-lifecycle is a skill published in the GitHub repository codervisor/leanspec (300 stars, last pushed 5mo ago), licensed MIT. It adds 169 tokens to every session and 3,129 once invoked, about $0.0007 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-30.
leanspec-pr-lifecycle compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| leanspec-pr-lifecyclecodervisor/leanspec | Skill | 300 | 5mo ago | MIT | A | 169 | Claude Code, Codex |
| gsd-complete-milestoneopen-gsd/gsd-core | Skill | 11k | yesterday | MIT | A | 16 | Claude Code |
| comet-archiverpamis/comet | Skill | 3.3k | yesterday | MIT | A | 34 | Codex |
| comet-releaserpamis/comet | Skill | 3.3k | yesterday | MIT | A | 65 | Claude Code, Codex |
| comet-safe-deliveryrpamis/comet | Skill | 3.3k | yesterday | MIT | A | 78 | Claude Code, Codex |
| codex-issue-coordinatorowainlewis/blueprint | Skill | 426 | 4d ago | MIT | A | 59 | Claude Code, Codex |
| development-workflowathola/claude-night-market | Skill | 348 | yesterday | MIT | A | 20 | Claude Code |