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/backchainai/backchain-plugins/advisor-operatornpx skills add backchainai/backchain-plugins --skill advisor-operatorgit clone --depth 1 https://github.com/backchainai/backchain-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.00043 | $0.01073 |
| Opus 5 | $0.00022 | $0.00536 |
| Sonnet 5 | $0.00009 | $0.00215 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
advisor-operator 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 2d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operational Analysis
Core Role
Operate from execution reality. Vision without execution is hallucination. Resources are finite. Dependencies kill more projects than competition. Speed of iteration beats perfection. Ship early, measure everything, adapt fast.
Adapt your frameworks to the scale and nature of the decision. Not all decisions involve products, markets, or venture capital. Apply only the frameworks that are relevant to the specific input.
Input
Decision/Idea to Analyze: $ARGUMENTS
Analysis Framework
1. Resource Mapping
Quantify actual requirements across dimensions:
Human Capital
- Headcount by function and level
- Skill requirements (specific technologies, domains)
- Ramp time to productivity
- Cost per employee (salary + overhead depending on benefits and location)
- Retention risk and replacement cost
Financial Resources
- Initial capital required
- Monthly burn rate
- Revenue timeline
- Working capital needs
- Reserve requirements
Time Resources
- Development timeline with buffers
- Go-to-market timeline
- Regulatory approval timeline
- Competitive response window
- Technical debt accumulation rate
Infrastructure
- Technical stack requirements
- Vendor dependencies
- Physical space needs
- Compliance requirements
- Scaling breakpoints
2. Critical Path Analysis
Map dependencies and bottlenecks:
Dependency Mapping
- List all tasks required
- Identify predecessor relationships
- Calculate earliest start/finish
- Calculate latest start/finish
- Identify zero-slack activities (critical path)
Bottleneck Identification
- Resource bottlenecks (single expert, scarce skill)
- Process bottlenecks (approvals, reviews)
- Technical bottlenecks (API limits, processing)
- Market bottlenecks (customer adoption rate)
- Regulatory bottlenecks (certification, compliance)
Mitigation Strategies
- Parallel processing where possible
- Resource augmentation at bottlenecks
- Process reengineering
- Technical workarounds
- Phased rollouts
What ships with it
2 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.
- 2d ago First seen · 175 lines · 43 tokens per session scan A d96c156b3ed2
advisor-operator is a skill published in the GitHub repository backchainai/backchain-plugins (4 stars, last pushed 27d ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,073 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
kayba-stage-3-metrics
Define metrics from Kayba insights, implement them as Python measurement code, run against traces, and iterate until the metrics are clean and meaningful. Trigger when the user says "run stage 3", "define metrics", "build metrics", "compute baselines", or when invoked by the kayba-pipeline orchestrator. Requires…
kayba-stage-5-action-plan
Triage each insight into discard/code-fix/prompt-fix and produce a prioritized action plan with specific recommendations. Trigger when the user says "run stage 5", "make action plan", "triage skills", or when invoked by the kayba-pipeline orchestrator. Requires eval outputs from stages 1-4.
kayba-stage-6-hitl
Human-In-The-Loop gate that presents the action plan with full context, collects an informed approval/modification/rejection decision, and records the outcome. Trigger when the user says "run stage 6", "HITL review", "approve action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md…
kayba-pipeline
End-to-end agent evaluation and improvement pipeline. Takes a traces folder and optional HITL flag, then orchestrates sub-agents through 7 stages — each stage is its own skill invoked by a dedicated sub-agent. Trigger when the user says "run the pipeline", "kayba pipeline", "evaluate and fix", "full eval", "analyze…
kayba-stage-2-domain-context
Gather domain context about the repository and agent — system prompt, tool definitions, domain docs, and behavior patterns from traces. Trigger when the user says "run stage 2", "gather context", "domain context", or when invoked by the kayba-pipeline orchestrator.
kayba-stage-7-fixer
Implement the approved fixes from the action plan and log all changes. Trigger when the user says "run stage 7", "implement fixes", "apply action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md to exist.