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 ash1794/vibe-engineering --skill vibe-start-informedgit clone --depth 1 https://github.com/ash1794/vibe-engineeringWrote 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/ash1794/vibe-engineering/vibe-start-informed)<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/vibe-start-informed"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/vibe-start-informed.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.00045 | $0.00732 |
| Opus 5 | $0.00023 | $0.00366 |
| Sonnet 5 | $0.00009 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
vibe-start-informed 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vibe-start-informed — 91% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibe-start-informed
Other people's documented failures count as observed failure. Research SOTA before proposing anything.
When to Use
- Brainstorming new features or capabilities
- Designing architecture for a new sub-system
- Choosing between technology approaches
- Any creative/design task where multiple valid approaches exist
Not for: Implementing already-designed specs, bug fixes, or tasks with clear requirements.
When NOT to Use
- Implementing an already-designed spec with clear requirements
- Bug fixes where the approach is already known
- Routine/mechanical changes with one obvious correct solution
- When the design decision has already been researched and recorded
The Rule
BEFORE proposing any approach, dispatch a research agent to find real papers, real projects, and real production systems that solve the same (or adjacent) problem.
digraph start_informed {
"Design question identified" [shape=doublecircle];
"Decompose into sub-problems" [shape=box];
"Dispatch research agent (WebSearch)" [shape=box];
"For each sub-problem find:" [shape=box];
"Synthesize imported failures" [shape=box];
"NOW propose approaches" [shape=doublecircle];
"Design question identified" -> "Decompose into sub-problems";
"Decompose into sub-problems" -> "Dispatch research agent (WebSearch)";
"Dispatch research agent (WebSearch)" -> "For each sub-problem find:";
"For each sub-problem find:" -> "Synthesize imported failures";
"Synthesize imported failures" -> "NOW propose approaches";
}
Research Requirements
For each sub-problem, find:
| Requirement | Minimum | Example |
|---|---|---|
| Named projects | 2+ with stars/adoption | "Graphiti (23k stars)" |
| Papers with venue | 1+ with year | "RAPTOR (ICLR 2024)" |
| Mechanism described | What it actually does | Not marketing copy |
| Known failures | What went wrong | "Flat RAG failed at multi-hop" |
| Applicability assessment | How it maps to our system | Specific, not generic |
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.
- 8d ago First seen · 77 lines · 45 tokens per session scan A 5120edb66a5a
vibe-start-informed is a skill published in the GitHub repository ash1794/vibe-engineering (10 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 732 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-31.
Other skills, from other repositories
resolve-plugins
Curate Claude Code skill / MCP / hook picks against live upstream sources and pin them in .claude/settings.json. Adding a process harness (a paired skill set) is an ordinary pick this door handles. Reads stack from docs/techstack.md, workflow signal from docs/overview.md + existing pins, then live-queries six source…
refresh
Use when an existing contextualizer's references may have drifted from current upstream state — typically weekly, or whenever a few days of upstream changes have accumulated — to bring them back into agreement.
using-skill-engine
When the user mentions skill-engine or "the engine" without naming a specific workflow, or wants first-run setup. Inspects .claude/skills/-context/ install state (and any pending -context.proposed/ proposals) across all three install levels, then dispatches to engine-bootstrap when no contextualizer exists, to…
apply
Use when a staged proposal has been reviewed and signed off — REVIEW.md Step 3 ticked reviewed or provisional — and is ready to promote into the live contextualizer.
config-set
Use when changing an engine-wide config value — currently diff.tool, the command /skill-engine:review prints for inspecting a proposed-vs-live diff.
my-adhd-caveman
Self-contained output mode: ADHD actable structure (action first, numbered steps, one next action, one-line progress) plus caveman diction (drop fluff/articles, fragments, fewer tokens). Use when the user says "adhd-caveman", "my-adhd-caveman", or invokes /my-adhd-caveman. Needs no other skills.