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/threat-vector-security/guardian-agent/coding-backend-orchestrationnpx skills add Threat-Vector-Security/guardian-agent --skill coding-backend-orchestrationgit clone --depth 1 https://github.com/Threat-Vector-Security/guardian-agentWrote 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/threat-vector-security/guardian-agent/coding-backend-orchestration)<a href="https://agentmods.dev/skills/threat-vector-security/guardian-agent/coding-backend-orchestration"><img src="https://agentmods.dev/badge/skills/threat-vector-security/guardian-agent/coding-backend-orchestration.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 | $0.00037 | $0.00450 |
| Opus 5 | $0.00018 | $0.00225 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
coding-backend-orchestration 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 5d 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.
What it actually says
Coding Backend Orchestration
Overview / When to Use
Use this workflow only when the user explicitly wants Guardian to launch or inspect an external coding assistant.
This is distinct from normal repo-grounded coding work:
- if the user asks Guardian to inspect, edit, patch, search, or test code directly, stay on the built-in coding tools
- if the user explicitly says to use Codex, Claude Code, Gemini CLI, or Aider, launch that backend with
coding_backend_run - mentioning a backend as the subject of a question is not enough to relaunch it
Process
- Confirm the active coding session or list available sessions with
code_session_currentorcode_session_listif the target workspace is unclear. - If needed, inspect available backends with
coding_backend_list. - Launch the requested backend with
coding_backend_runfrom the active coding session workspace. - If the user is asking whether a delegated run finished or what happened, use
coding_backend_status. - After a backend run completes, verify the result with
code_git_diffand the strongest relevant checks such ascode_test,code_build, orcode_lint. - Report backend output as delegated work, not as if Guardian performed the edits directly.
Red Flags
- Treating "Why did Codex do that?" as permission to start a new Codex run.
- Launching an external backend when the user only asked for direct repo inspection.
- Reporting delegated backend work as successful without verification.
- Running a backend outside the active coding session workspace.
Verification
- The user explicitly requested an external coding backend.
- The delegated run stayed anchored to the active coding session workspace.
- You checked completion or recent runs with
coding_backend_statuswhen needed. - You verified the delegated result with
code_git_diff,code_test,code_build, orcode_lintbefore reporting success.
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.
- 5d ago First seen · 39 lines · 37 tokens per session scan A abf686ce8ce2
coding-backend-orchestration is a skill published in the GitHub repository Threat-Vector-Security/guardian-agent (11 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 450 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
orloj-generator
Interactive scaffold generator for Orloj multi-agent systems. Use this skill whenever someone wants to create, set up, scaffold, bootstrap, or generate an Orloj agent system, pipeline, swarm, or hierarchy. Also trigger when users mention "orlojctl init", ask how to get started with Orloj, want to build a multi-agent…
continuum-tools-mcp
Connect MCP servers (Stdio/SSE/StreamableHTTP) to a Continuum agent, configure tool filtering, set up tool-context capture/injection (e.g. sessionid), and read run artifacts (UI widgets, structured tool data). Invoke when the user asks "connect MCP", "filesystem tool", "remote API tool", "auto-capture sessionid"…
continuum-handoffs
Build agent-to-agent transitions with Continuum's Handoff system — triage routing, history summarization modes (FULL/SUMMARY/RECENTN/HYBRID), cycle detection, depth tracking, return-to-parent. Invoke when the user asks "route customer requests to specialists", "agent that can transfer to another", "summarize history…
continuum-llm-providers
Pick the right LLM provider, configure structured outputs, control context-window compression, and use the LLMClient directly. Provider routing is by model-string prefix; LiteLLM has been removed. Also covers Smart Gateway integration for multi-provider routing. Invoke when the user asks about "switch to Claude"…
continuum-temporal
Build durable agent workflows with Temporal — sequential/parallel/loop/conditional steps, human-in-the-loop approval gates, custom workflows and activities. Invoke when the user asks "long-running workflow", "approval gate", "human in the loop", "retry on failure", "workflow survives restart", or anything…
continuum-testing
Write tests for Continuum agents — mock LLM and memory clients via the DI Container, use fakeredis for sessions, snapshot agent responses, and run pytest-asyncio. Invoke when the user asks "test my agent", "mock the LLM", "fakeredis", "container injection", "pytest", or wants their CI to validate agent behavior…