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-setupgit 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-setup)<a href="https://agentmods.dev/skills/martinffx/atelier/atelier-setup"><img src="https://agentmods.dev/badge/skills/martinffx/atelier/atelier-setup/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-setup"><img src="https://agentmods.dev/badge/skills/martinffx/atelier/atelier-setup.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.00984 |
| Opus 5.5 | $0.00021 | $0.00394 |
| Sonnet 5.5 | $0.00010 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00098 |
Grade A, and why
atelier-setup 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atelier Setup
Set up repository guidance that Atelier skills need without taking ownership of the developer's installation, harness configuration, or project structure. Explore first, present every proposed edit exactly, and write only after the developer approves it.
1. Explore
Read the repository before proposing any change:
- Root
AGENTS.mdandCLAUDE.md, if present. Note whether either already has an## Agent skillsheading. - Root
CONTEXT.mdandCONTEXT-MAP.md. docs/adr/and any context-localdocs/adr/directories.docs/agents/, including existingissue-tracker.mdanddomain.md.- Existing issue-tracker conventions: remotes, issue links in documentation, local issue directories, and project guidance.
- Genuine monorepo signals: a workspace manifest, or multiple independently deployable packages with their own source directories.
Do not create, install, configure, or modify anything during exploration.
2. Present Findings
Summarize what exists and recommend a domain-document layout:
- Single-context is the default: domain language belongs in root
CONTEXT.md; architectural decisions belong in rootdocs/adr/. - Multi-context is appropriate only when the repository has genuinely separate bounded
contexts.
CONTEXT-MAP.mdbelongs at the root and points to each context'sCONTEXT.mdanddocs/adr/directory.
Explain that domain documents remain lazy: do not create CONTEXT.md, CONTEXT-MAP.md, or an ADR
directory until another Atelier skill has resolved terminology or made a decision worth recording.
Select or confirm the issue tracker:
- If
docs/agents/issue-tracker.mdalready defines one, preserve it unless the developer asks to change it. - Otherwise recommend the tracker indicated by existing repository practice, then ask the developer to confirm or describe their tracker.
- Accept GitHub, GitLab, local Markdown, another tracker described by the developer, or
none. - Record the chosen workflow in
docs/agents/issue-tracker.md; do not install, initialize, or create external tracker resources.
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.
- 1mo ago First seen · 104 lines · 52 tokens per session scan A 36ccf59b282f
atelier-setup is a skill published in the GitHub repository martinffx/atelier (48 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 984 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
obsidian-organizer
File new notes into the right folder and audit/reorganize folder structure in the user's Obsidian vault, using the obsidian CLI and a single source-of-truth map note (00Index/FolderMap.md) that lives inside the vault. Use this whenever a note needs to be placed, filed, sorted, or moved into the vault; whenever the…
notes
A note-management guide for searching, reading, creating, and adding content to personal notes through an API.
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.