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 fortunto2/solo-factory --skill grillgit clone --depth 1 https://github.com/fortunto2/solo-factoryWrote 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/fortunto2/solo-factory/grill)<a href="https://agentmods.dev/skills/fortunto2/solo-factory/grill"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/grill/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/fortunto2/solo-factory/grill"><img src="https://agentmods.dev/badge/skills/fortunto2/solo-factory/grill.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00099 | $0.00656 |
| Opus 5 | $0.00049 | $0.00328 |
| Sonnet 5 | $0.00020 | $0.00131 |
| Haiku 4.5 | $0.00010 | $0.00066 |
Grade A, and why
solo-grill 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/grill — the interview primitive
Interview the user relentlessly about every aspect of the thing until you reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one by one. For each question, give your own recommended answer.
Ask one question at a time, waiting for the answer before the next. A batch of questions is bewildering and destroys the dependency order that makes the interview converge.
Look up facts; ask for decisions. If something can be settled by exploring the environment — filesystem, git history, the codebase, the web — go and settle it. The decisions are the user's: put each one to them and wait.
Do not act on the plan until the user confirms the shared understanding is reached.
Why one at a time
The mental model is a decision tree. An early answer reshapes which questions come next — a firehose of parallel questions throws away that structure and produces answers to questions that turned out not to matter.
Composing
This is a primitive, not a workflow. Reach for it from inside other work whenever a plan needs sharpening:
- Before
/plan— when the feature is still fuzzy./plandeliberately asks zero questions and researches code instead, so grill first when the decisions, not the code, are what's missing. - Before
/validate— when the idea itself hasn't been pinned down enough to score. - Inside
/stream— when a STREAM layer needs the user's judgement rather than analysis. - After
/diagnosePhase 3 — to pressure-test which hypothesis to chase.
Gotchas
- Recommendations are the point. A bare question makes the user do all the work; a question with your recommended answer lets them correct a draft, which is far faster.
- Asking what you could look up burns trust. Check the repo, the config, the git log first.
Don't
- Batch questions "to save time" — it costs more.
- Start building the moment the user answers the last question; confirm the shared understanding first.
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 · 50 lines · 99 tokens per session scan A 44cdae7cd36f
solo-grill is a skill published in the GitHub repository fortunto2/solo-factory (18 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 656 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-30.
Other skills, from other repositories
harness
Route Harness Starter Kit workflows. Use when the user invokes /harness with adopt, doctor, update, refresh, review, or review sub-agent, or asks to apply, diagnose, maintain, or review repository harness guidance.
review
L1 internal review with auto-detection, design comparison, and Gate escalation path.
dev-plan
Generate a development plan with task breakdown and section 10 tracking tables.
product-diagnosis
Six-question diagnostic framework for G0 pre-check — validate product direction before development starts.
harness-adopt
Apply Harness Starter Kit prompt-first adoption to a target repository. Use when the user asks to apply, install, adopt, or bootstrap repository harness guidance, checks, memory, and adoption reporting.
harness-review
Review the current change set from an opposing harness-engineering perspective. Use when the user asks for /harness review, /harness review sub-agent, or a no-edit harness review.