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.
git clone --depth 1 https://github.com/big-emotion/agent-atelierWrote 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/commands/big-emotion/agent-atelier/interview)<a href="https://agentmods.dev/commands/big-emotion/agent-atelier/interview"><img src="https://agentmods.dev/badge/commands/big-emotion/agent-atelier/interview/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/commands/big-emotion/agent-atelier/interview"><img src="https://agentmods.dev/badge/commands/big-emotion/agent-atelier/interview.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.00028 | $0.00080 |
| Opus 5.5 | $0.00011 | $0.00032 |
| Sonnet 5.5 | $0.00006 | $0.00016 |
| Haiku 4.5 | $0.00003 | $0.00008 |
Grade A, and why
interview 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 1mo 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
$ARGUMENTS
You should interview me until you have 95% of confidence what I actually want, not what I think I should want. Ask probing questions, challenge my assumptions, and dig deeper before proposing any solution or plan.
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.
- 1mo ago First seen · 8 lines · 28 tokens per session scan A e9b24f08f59c
interview is a command published in the GitHub repository big-emotion/agent-atelier (3 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 80 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
tmux-layout
Use this skill when the operator wants a prepared tmux visualization layout for the session's side-channels (STATE.md tail, CI-watch, events.jsonl tail). Renders a 4-pane default layout or debug layout. Read-only side-channel observability — the coordinator chat stays in the operator's original terminal. Trigger…
ccc-makeover
Score project health with X-Ray, apply the top recommendations in impact order with your OK for each, and show the before and after score. Use when you want the highest-impact project health fixes applied and measured.
sm-sail
Command "sm-sail" from ScienceIsNeato/slop-mop, covering /sm-sail — drive a pr to green, autonomously, the loop, when sail parks on review threads, when to stop before "pr ready" — only two reasons and expect convergence, not one pass.
redteam
A read-only review of infrastructure settings, infrastructure-as-code, and CI/CD pipelines using MITRE ATT&CK attack paths. MITRE ATT&CK is a catalogue of techniques attackers use, while CI/CD means the automated process that builds, tests, and deploys software.
sm-buff
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…
nyann:wait-for-pr-checks
Poll a GitHub PR's checks until they all pass, any one fails, or a timeout is hit. Returns a structured outcome the caller can gate on.