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 kraulerson/solo-orchestrator --skill grill-with-docsgit clone --depth 1 https://github.com/kraulerson/solo-orchestratorWrote 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/kraulerson/solo-orchestrator/grill-with-docs)<a href="https://agentmods.dev/skills/kraulerson/solo-orchestrator/grill-with-docs"><img src="https://agentmods.dev/badge/skills/kraulerson/solo-orchestrator/grill-with-docs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kraulerson/solo-orchestrator/grill-with-docs"><img src="https://agentmods.dev/badge/skills/kraulerson/solo-orchestrator/grill-with-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.01735 |
| Opus 5 | $0.00036 | $0.00868 |
| Sonnet 5 | $0.00014 | $0.00347 |
| Haiku 4.5 | $0.00007 | $0.00173 |
Grade A, and why
grill-with-docs 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 10d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Attribution. Adapted from mattpocock/skills (MIT, © Matt Pocock). The upstream uses a
CONTEXT.mdglossary as the persistence target. Solo's adaptation retargets toPROJECT_BIBLE.md(Solo's canonical architecture/data-model/threat-model document) anddocs/ADR documentation/(Solo's ADR location, distinct from upstream'sdocs/adr/). The interview pattern, ADR-criteria, and inline-update discipline are preserved. SeeNOTICEfor full attribution.
Interview the user relentlessly about every aspect of this plan until a shared understanding is reached. Walk down each branch of the design tree, resolving dependencies between decisions one at a time. For each question, provide a recommended answer.
Ask one question at a time. Wait for feedback before continuing.
If a question can be answered by exploring the codebase or reading existing documentation, do that instead of asking.
Where Solo's documentation lives
Solo Orchestrator projects keep their truth in a small set of canonical files. Read them before asking the user; cite them in answers.
| File | Role | When to update |
|---|---|---|
PROJECT_BIBLE.md |
Architecture, data model, threat model, domain vocabulary. The canonical truth. | When terms resolve, when domain boundaries clarify, when the data model changes. Update inline during grilling. |
docs/ADR documentation/ |
Architectural Decision Records. Per Solo's templates/generated/adr.tmpl. |
When a decision meets the 3-of-3 ADR criteria (below). Create lazily; never preemptively. |
CLAUDE.md |
Per-session conventions, agent preferences, project-wide reminders. | When a session-readable convention emerges (e.g., "always commit in feat: form for Cutline work") — distinct from architectural truth. |
solo-orchestrator-backlog.md (or project equivalent) |
Open BL items, parked items, pending decisions. | When a question is deferred (not resolved). File a BL entry pointing to the grilling session's open question. |
.claude/phase-state.json / .claude/process-state.json |
Where we are in Phase / Build Loop. | Read-only during grilling — informs which decisions are in-scope for this phase. |
Solo intentionally does NOT have a separate CONTEXT.md glossary today. PROJECT_BIBLE.md carries the domain vocabulary as part of its architecture section. If a project's vocabulary grows large enough to warrant its own glossary file, that decision should itself go through an ADR.
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.
- 10d ago First seen · 118 lines · 72 tokens per session scan A 43001c01f569
grill-with-docs is a skill published in the GitHub repository kraulerson/solo-orchestrator (29 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 1,735 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.