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 skills/vironnimo/vbot/coding-agentsnpx skills add Vironnimo/vbot --skill coding-agentsgit clone --depth 1 https://github.com/Vironnimo/vbotWhat 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.00103 | $0.01327 |
| Opus 5 | $0.00051 | $0.00664 |
| Sonnet 5 | $0.00021 | $0.00265 |
| Haiku 4.5 | $0.00010 | $0.00133 |
Grade A, and why
coding-agents 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coding Agents
Use a real interactive Terminal Session for the coding agent's entire lifecycle. The external agent, the vBot agent, and the user share the same live terminal. Terminal Sessions survive individual Runs, so an external agent may keep working after the Run that started it ends.
Non-negotiable rules
- Use
terminaland launch the CLI's normal interactive command. Do not convert the task into a one-shot or machine-output invocation. - Keep the exact
terminal_idreturned bystart. Use that same live Terminal Session for questions, approvals, follow-up instructions, and later work instead of starting another process. - Treat quiet output as an activity boundary, never as proof of completion. Use
wait, then inspectstatusand the rendered screen. - Do not disable approvals, permission checks, or sandboxes merely to avoid interaction. Answer safe, unambiguous prompts through the TUI; ask the user when the choice carries meaningful authority, risk, cost, or product intent.
- The user may take control of the same terminal in the WebUI. Before sending sensitive input such as an approval or menu selection, reread
statusand useexpected_screen_revisionso stale input is rejected. - Never put credentials or secrets in task text. If login or trust setup appears, leave the Terminal Session available for the user and explain what needs attention.
Start or reuse
First call list. Reuse the intended live Terminal Session when one already exists. Its program-announced title, command, working directory, state, and recent screen help identify it.
For a configured CLI, call start with the interactive command, the intended workdir, any explicitly chosen model or safety arguments, and the initial instruction in text. For a registered Project, workdir: "project:<project-id>" resolves its current cwd by stable id without loading Project Context or changing Terminal ownership. start sends the text followed by Enter after the PTY is ready.
What ships with it
3 files 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.
- yesterday First seen · 60 lines · 103 tokens per session scan A 6bffd8aac997
coding-agents is a skill published in the GitHub repository Vironnimo/vbot (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,327 once invoked, about $0.0005 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
gpt-researcher
GPT Researcher is an autonomous deep research agent that conducts web and local research, producing detailed reports with citations. Use this skill when helping developers understand, extend, debug, or integrate with GPT Researcher - including adding features, understanding the architecture, working with the API…
review-pr
Review a Dograh pull request, branch diff, or pasted patch for repo-specific security and correctness risks that are not obvious from generic FastAPI, Next.js, or Python conventions. Use when the user asks to review a PR, audit a diff, check whether changes are safe to merge, review their own changes, or asks what to…
gpt-researcher
Autonomous deep research from Codex via MCP.
review-agents-md
Audit Dograh AGENTS.md files for drift against the live repo and for bad scope boundaries between parent and child docs. Use when the user asks to review existing AGENTS files, identify stale guidance, decide whether a subtree needs its own AGENTS.md, or update the AGENTS.md hierarchy under the repo root, api/, or ui/.
merge-pipecat-upstream
Merge the latest upstream pipecat-ai/pipecat tag into the pipecat submodule fork (dograh-hq/pipecat) and bump the dograh repo to it. Use whenever the user asks to bump, upgrade, sync, or merge pipecat, resolve pipecat merge conflicts, audit whether upstream changes break or supersede Dograh's in-fork patches, or…
memmachine-memory
Use when an agent or model needs durable project, user, or session context from MemMachine, needs to save information to MemMachine memory, has requests involving mem-cli, memmachine, or memmachineclient, has insufficient conversation context, or is tempted to search local files for prior context that should come from…