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 jamditis/claude-skills-journalism --skill vibe-codinggit clone --depth 1 https://github.com/jamditis/claude-skills-journalismWrote 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/jamditis/claude-skills-journalism/vibe-coding)<a href="https://agentmods.dev/skills/jamditis/claude-skills-journalism/vibe-coding"><img src="https://agentmods.dev/badge/skills/jamditis/claude-skills-journalism/vibe-coding/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/jamditis/claude-skills-journalism/vibe-coding"><img src="https://agentmods.dev/badge/skills/jamditis/claude-skills-journalism/vibe-coding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Tool Misuse · line 28 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Memory Poisoning · line 102 Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
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.00035 | $0.01875 |
| Opus 5 | $0.00017 | $0.00937 |
| Sonnet 5 | $0.00007 | $0.00375 |
| Haiku 4.5 | $0.00003 | $0.00187 |
Grade A, and why
vibe-coding 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 9d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe coding methodology
Practical strategies for building software effectively with AI coding assistants.
Tool landscape moves fast. This skill was last swept 2026-05-08. The methodology (planning, version control, testing, bug-fixing) is stable; the specific tool names, instruction-file conventions, and pricing details drift quarterly. Treat the named tools as representative, not exhaustive.
Planning process
Start by working with the AI to write a detailed implementation plan in a markdown file.
Scope management: Review and refine the plan, delete unnecessary items, mark complex features as "won't do," and keep a separate section for ideas to implement later. This prevents scope creep and maintains focus.
Incremental implementation: Work section by section rather than building everything at once. Have the AI mark sections complete after successful implementation, and commit each working section to git before moving to the next.
Track progress visibly: Use todo lists, markdown checklists, or inline status markers so both you and the AI can see what's done and what remains. This prevents re-implementing completed work and keeps sessions focused.
Version control strategies
Git is your safety net, don't rely solely on the AI tool's revert functionality.
Branch per attempt: Begin each new feature on a fresh feature branch (git switch -c feature/xyz) and commit small chunks as the AI makes progress. The branch boundary is your "if this goes off the rails, throw it away" boundary, you discard the branch, not your working tree.
When the AI goes down a bad path: Prefer reversible commands. git restore . discards uncommitted changes; git stash parks them; git switch - jumps back to your previous branch. Reach for git reset --hard HEAD only when you've confirmed there's nothing in the working tree worth keeping, destructive commands skip the reflog niceties and can swallow uncommitted experiments. (If the agent has been creating new files, a separate git clean -fd is also part of "really, throw it all away", same caveats.)
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.
- 9d ago First seen · 120 lines · 35 tokens per session scan A 4a89c6defb82
vibe-coding is a skill published in the GitHub repository jamditis/claude-skills-journalism (389 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,875 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
food-research
Run a comprehensive, multi-source literature and evidence-synthesis workflow for food & nutrition science. Use when the user wants to research a food/nutrition topic in depth, do a literature review, build an evidence brief, screen and synthesize many sources, verify citations, or scope a systematic review.…
data-table-formatter
Formats raw or messy data into a clean, publication-ready table with appropriate headers, sorted rows, consistent number formatting, and a source note — ready to drop into an article, report, or web page.
springer-food
Shared author-guideline skill for Springer / Springer Nature food journals: Food Engineering Reviews, Food and Bioprocess Technology, Food Security, and the SpringerOpen journal Food Production Processing and Nutrition. Use to format or check a manuscript for a Springer food journal — structure, abstract/keyword…
wiley-food
Shared author-guideline skill for Wiley food & nutrition journals: Comprehensive Reviews in Food Science and Food Safety, Food Frontiers, eFood, Legume Science, Food and Energy Security, Molecular Nutrition & Food Research, Journal of Food Biochemistry, Food Science & Nutrition. Use to format or check a manuscript for…
annu-rev-food
Author-guideline skill for Annual Review of Food Science and Technology (Annual Reviews, ISSN 1941-1413). Use to format or check an invited review for this journal — review structure, author–date Annual Reviews references, and figure specs. Triggers: submit to Annual Review of Food Science and Technology, Annual…
british-food-journal
Author-guideline skill for British Food Journal (Emerald, ISSN 0007-070X). Use to format or check a manuscript for BFJ — Emerald's required structured abstract, article classification, Harvard references, and figure specs. Triggers: submit to British Food Journal, Emerald food journal guidelines, structured abstract…