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 martinffx/atelier --skill atelier-orchestratorgit clone --depth 1 https://github.com/martinffx/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/skills/martinffx/atelier/atelier-orchestrator)<a href="https://agentmods.dev/skills/martinffx/atelier/atelier-orchestrator"><img src="https://agentmods.dev/badge/skills/martinffx/atelier/atelier-orchestrator/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/martinffx/atelier/atelier-orchestrator"><img src="https://agentmods.dev/badge/skills/martinffx/atelier/atelier-orchestrator.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.00052 | $0.02059 |
| Opus 5.5 | $0.00021 | $0.00824 |
| Sonnet 5.5 | $0.00010 | $0.00412 |
| Haiku 4.5 | $0.00005 | $0.00206 |
Grade A, and why
atelier-orchestrator 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 6d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. This is not optional. You cannot rationalize your way out of this.
Planning Workflow
You have skills. You MUST use them. Not "should." Not "when convenient." MUST.
Invoke relevant skills BEFORE any response or action. Even a 1% chance a skill might apply means you invoke it. If an invoked skill turns out to be wrong for the situation, you don't need to follow it. But you must check.
The One Rule
When an implementation choice exists, never write code until the human has reviewed and approved a written plan. Exact mechanical changes may use the exception below.
The plan may be inline in the conversation or backed by persisted spec artifacts. Select the mode before invoking an artifact-producing skill, state the choice with one brief reason, and let the human override it.
Governing Principles
Invoking a skill selects relevant guidance. It does not make every pattern in every loaded skill part of the solution. Existing source, explicit requirements, and the smallest correct change determine which patterns apply.
Begin with the current design and the minimum behavior-preserving change. Product, infrastructure, and architectural expansion require explicit scope. Keep ponytail active throughout development when it is available or required by the repository. Keep writing-clearly-and-concisely active whenever writing or editing prose for humans. Before returning or persisting that prose, apply humanizer in embedded mode.
Planning Modes
Inline Plan (default)
Use for bounded, well-understood work, including ordinary features, bug fixes, refactors,
configuration changes, and multi-file changes. Route to spec-plan with Inline mode
explicitly selected. It presents a concise plan in conversation, creates no planning artifacts
or tracker entries, and stops for approval. Approval ends the spec-plan invocation. A later,
explicit implementation request may implement the plan directly; do not invoke
spec-implement, spec-finish, or code-subagents for Inline work.
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.
- 6d ago Changed · +2 lines 14eac98e9ff3
- 7d ago Changed · +5 lines 4244b6981ac3
- 15d ago Changed · +9 lines 929b1d4c486a
- 1mo ago First seen · 204 lines · 52 tokens per session scan A 517fe0b0d183
atelier-orchestrator is a skill published in the GitHub repository martinffx/atelier (48 stars, last pushed 7d ago), licensed MIT. It adds 52 tokens to every session and 2,059 once invoked, about $0.0002 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-30.
Other skills, from other repositories
harbor
Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, impact and evidence.…
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
refit
Cross-session environment retrospective driven by OMC's own instrumentation — trace timelines, friction reports, logs, and plan notepads. Every finding lands on the surface that owns the fix (deterministic check, steering volume, tooling, or information access); nothing is written without user approval.
minimal-code-discipline
YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away.
omc-review
Evaluate finished work for defects, risk, and simplification before it ships.
triage
A process for reviewing issues and outside pull requests through category and status labels. An issue is a recorded problem or request, while a pull request is a proposed code change for review.