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 LandonSchropp/agent-toolkit --skill vibegit clone --depth 1 https://github.com/LandonSchropp/agent-toolkitWrote 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/landonschropp/agent-toolkit/vibe)<a href="https://agentmods.dev/skills/landonschropp/agent-toolkit/vibe"><img src="https://agentmods.dev/badge/skills/landonschropp/agent-toolkit/vibe/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/landonschropp/agent-toolkit/vibe"><img src="https://agentmods.dev/badge/skills/landonschropp/agent-toolkit/vibe.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.00041 | $0.01151 |
| Opus 5.5 | $0.00016 | $0.00460 |
| Sonnet 5.5 | $0.00008 | $0.00230 |
| Haiku 4.5 | $0.00004 | $0.00115 |
Grade A, and why
vibe 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 15d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe
The user never reads the code here. They run the product and react to it, so nobody else will catch a bug in the code, and the only thing worth reporting is what they can see.
For a new project, REQUIRED: use the ls-code:project-conventions skill to create the root files first. At the start of every session, make sure the README, AGENTS.md and coverage setup below are in place.
README
README.md is one of the few files the user reads and approves. It describes the product's primary interface, so the user sets its direction. Every change to it goes through ls-interactivity:interactive-review in staged mode with only README.md staged, and is committed on its own before any other work continues. No other file ever appears in a review.
The README opens, above everything else, with this callout:
> [!WARNING]
> **This repository is 100% vibe coded.** The author did not read any of the code. Use it at your own risk.
AGENTS.md
Directly after the line requiring agents to read README.md, AGENTS.md has this instruction:
**REQUIRED:** Invoke the `ls-agent:vibe` skill and follow its instructions. At the start of every session, ask the user to run `/ls-interactivity:disable-review`.
Coverage
Set up tooling that fails below 100% test coverage, such as a coverage check, script or CI step. Checking the number by eye doesn't count, and neither do coverage exclusions or ignore comments the user hasn't approved.
Forks of someone else's project are the exception. Don't add tests for the code inherited from upstream, but keep any tests and coverage checks upstream already has passing. Only the functionality the fork adds must reach 100%, including its changes inside inherited files, and tooling enforces that too, such as per-file thresholds on the fork's own files plus a changed-lines check against upstream. A repository the user fully owns has no inherited code, so everything in it counts.
Working With the User
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.
- 15d ago Changed · +3 lines 2aa5df8df2eb
- 16d ago First seen · 67 lines · 41 tokens per session scan A 9275f1e14f72
vibe is a skill published in the GitHub repository LandonSchropp/agent-toolkit (3 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,151 once invoked, about $0.0002 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-09-30.
Other skills, from other repositories
press-clip
Turn a live article URL into a press clip that looks like the real coverage — the publication's own logo, fonts, photos and layout kept intact, the ads and clutter removed, and (for a roundup) just the client's section. Renders to PDF. You inspect each site and tailor the removal; the bundled script carries no…
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
coverage-tracker
Run a Google Alerts-style keyword coverage tracker. Uses news-search for recent keyword queries, lets the LLM dedupe and classify real features versus junk, stores decisions in SQLite, and alerts only on new real coverage.
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…
coverage-tracker-setup
Set up a lightweight Google Alerts-style coverage tracker for any number of keywords. Creates a tracker config with each keyword and what it actually means, then hands recurrence to the user's agent harness.
prompt-set-qa
Gate a prompt universe for schema and provenance completeness, target or campaign contamination, evidence entailment, naturalness, one-concept clarity, architecture consistency, aided status, answer leakage, and semantic duplicates. Use after realistic prompt generation and before human panel selection.