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 giang6283623/minimal-vibe-coding-kit --skill reviewing-4p-prioritiesgit clone --depth 1 https://github.com/giang6283623/minimal-vibe-coding-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/giang6283623/minimal-vibe-coding-kit/reviewing-4p-priorities)<a href="https://agentmods.dev/skills/giang6283623/minimal-vibe-coding-kit/reviewing-4p-priorities"><img src="https://agentmods.dev/badge/skills/giang6283623/minimal-vibe-coding-kit/reviewing-4p-priorities/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/giang6283623/minimal-vibe-coding-kit/reviewing-4p-priorities"><img src="https://agentmods.dev/badge/skills/giang6283623/minimal-vibe-coding-kit/reviewing-4p-priorities.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
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 →
- low Excessive Agency · line 71 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.00045 | $0.00600 |
| Opus 5 | $0.00023 | $0.00300 |
| Sonnet 5 | $0.00009 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
reviewing-4p-priorities 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 11d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewing 4P Priorities
Use this skill to classify work from P0 to P4 and convert review findings into a practical fix order.
Priority Scale
| Priority | Meaning | Response |
|---|---|---|
| P0 | Critical outage, data loss, security exposure, or all users blocked | Stop and fix immediately |
| P1 | Major user-facing or release-blocking failure for many users | Fix before other planned work |
| P2 | Important bug, maintainability risk, or strategic enhancement | Schedule in the current cycle |
| P3 | Local polish, minor edge case, or narrow productivity improvement | Routine backlog |
| P4 | Nice-to-have, exploratory idea, or low-confidence request | Capture, defer, or discard |
Vibe Coding Review Flow
- Identify the affected user, workflow, or agent surface.
- Separate evidence from guesses.
- Classify the current impact, not hypothetical worst cases.
- Explain why the item is not one level higher or lower.
- Convert each P0-P2 item into a small fix task and validation check.
- Leave P3-P4 items as optional follow-up unless they reduce risk cheaply.
Output
## 4P Review
Classification: P<0-4>
Issue: <short description>
Evidence:
- <observed fact>
Impact:
- Users/workflows affected: <scope>
- Failure mode: <what breaks>
Rationale:
- Why this priority:
- Why not higher:
- Why not lower:
Fix order:
1. <small task>
2. <small task>
Validation:
- <command or manual check>
Priority Boundaries
- P0 requires immediate action because harm is happening now or secrets/data are exposed.
- P1 is urgent but does not require emergency response for every user.
- P2 is important and should be planned, but users have a workaround or impact is bounded.
- P3 improves quality but does not materially block the workflow.
- P4 is a candidate for a note, not an implementation commitment.
Examples
Use examples.md when a priority boundary is ambiguous, especially P0 vs P1, P1 vs P2, security edge cases, or agent-surface risk classification.
What ships with it
1 file 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.
- 11d ago First seen · 73 lines · 45 tokens per session scan A 7f9acfbfc33c
reviewing-4p-priorities is a skill published in the GitHub repository giang6283623/minimal-vibe-coding-kit (21 stars, last pushed 14d ago), licensed MIT. It adds 45 tokens to every session and 600 once invoked, about $0.0002 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.