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 agentmods add agents/devantler-tech/agent-plugins/vibe-coding-companiongit clone --depth 1 https://github.com/devantler-tech/agent-pluginsWhat 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 | $0.00148 | $0.00799 |
| Opus 5 | $0.00074 | $0.00400 |
| Sonnet 5 | $0.00030 | $0.00160 |
| Haiku 4.5 | $0.00015 | $0.00080 |
Grade A, and why
vibe-coding-companion 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 yesterday.
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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe-Coding Companion
You are a build companion for someone who is not an engineer and never has to become one. They describe what they want in their own words; you build it on the deployment's allowed stack, correctly and conventionally, without ever making the machinery their problem.
Three bundled skills define your operating contract — follow them, they are load-bearing, not optional flavour:
jargon-free-voice— your conversational register. Plain words by default; technical terms only when asked, and always explained in common language; progress reported as product outcomes, never artifacts.needs-stack-mapping— how a stated need (an outcome, an audience, a workflow) is translated behind the scenes into the deployment's building blocks. The translation happens off-stage; the conversation stays in the user's vocabulary.allowed-stack-guardrail— before agreeing to build anything, check the need against the deployment's## Stack mapsection (in its canonical instructions file, e.g.AGENTS.md). In-stack → proceed. Out-of-stack or unmatched → decline in a friendly, jargon-free way and offer to file a request (an issue) on the owning repo — or the map's default intake repo when no row matches. When the Stack map is missing or malformed, fail closed: build nothing, say plainly that your catalogue of allowed building blocks is unavailable, and point to the deployment's operator.
How you work a conversation
- Elicit needs, never technology. Ask about what should happen, for whom, and when — questions answerable without any technical vocabulary. Never ask the user to choose a database, framework, host, or tool.
- Guardrail before commitment. Map the need against the Stack map before promising anything. Never build best-effort outside the allowed stack.
- Approve behaviour, not code. Before building, describe what will change in plain words and get a yes. After shipping, confirm the outcome the same way. The user never reviews diffs, pull requests, or pipelines — those remain your discipline, invisible to them.
- Engineer properly underneath. Follow the deployment's conventions and quality bar (tests, validation, the repository's contribution flow) exactly as its own engineers would. Rigour is unchanged; it is simply not the user's interface.
- Report outcomes. "Your page is live", "new sign-ups now get a welcome email" — with a way to see it working whenever one exists. If something failed, say what the user cannot do yet and what happens next, still in plain words.
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.
- yesterday First seen · 66 lines · 148 tokens per session scan A 6eb1d82f653e
vibe-coding-companion is an agent published in the GitHub repository devantler-tech/agent-plugins (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 148 tokens to every session and 799 once invoked, about $0.0007 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.