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 big-emotion/agent-atelier --skill specgit 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/skills/big-emotion/agent-atelier/spec)<a href="https://agentmods.dev/skills/big-emotion/agent-atelier/spec"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/spec/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/big-emotion/agent-atelier/spec"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/spec.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.00102 | $0.05755 |
| Opus 5 | $0.00051 | $0.02877 |
| Sonnet 5 | $0.00020 | $0.01151 |
| Haiku 4.5 | $0.00010 | $0.00575 |
Grade A, and why
{{project_slug}}-spec 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 3d 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.
This is a copy
92% identical to project-standard-spec — 47 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{project_display_name}} Spec
Maintain the {{project_display_name}} spec tree on Confluence. Given a free-text problem (bug, feature, refinement idea), read Confluence (Requirements / Decisions / Architecture) as the canonical source of truth, structure the reflection, propose Pending REQ/DEC/ARCH sections plus matching Jira tickets in {{jira_project_key}}, then — after explicit confirmation — publish Confluence first, Jira second, and close the link loop both ways.
This skill is append-only on Confluence and only writes new sections at status Pending. Humans transition Pending → Implemented → Approved through the Confluence UI. The skill never touches the Status macro of an existing section, never edits the body of a non-Pending section, and never deletes an ID.
When to Activate
- User invokes
/{{project_slug}}-spec <description>(explicit command). - User writes a natural-language prompt that signals a spec-level reflection:
bug : …/bug:/ "il y a un bug" / "the … is broken"j'aimerais ajouter …/ "je voudrais ajouter" / "we should add"feature idea …/ "feature idea" / "what if we"comment résoudre …/ "comment fixer" / "how do we handle"- Any free-text describing a problem, gap, or improvement that lacks a Jira ticket and that may touch a REQ/DEC/ARCH.
- Do not activate when:
- The user pastes a Jira ticket URL or key — that path belongs to
{{project_slug}}-ticket. - The user asks to flip a Status macro on an existing section (
Pending → Implemented, etc.) — that is a Confluence-UI-only operation, refuse and direct them there. - The user asks to bootstrap or repopulate the spec tree — that is
/{{project_slug}}-bootstrap-confluenceand runs only once.
- The user pastes a Jira ticket URL or key — that path belongs to
If the trigger is ambiguous (the description could be either a pure code question or a spec change), default to activating: the worst case is the user replies with anything other than an affirmative token at Step 6 and nothing is written.
Inputs
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.
- 3d ago First seen · 310 lines · 0 tokens per session scan A 622ed56e26b1
{{project_slug}}-spec is a skill published in the GitHub repository big-emotion/agent-atelier (2 stars, last pushed 3d ago), licensed MIT. It adds 102 tokens to every session and 5,755 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to project-standard-spec, differing in 47 lines, and is treated as a copy.
Other skills, from other repositories
tpp-orchestrate
Work through a queue of Technical Project Plans serially — delegate each to a TDD subagent, get a cross-model second opinion, empirically vet every finding, and make one coherent commit per plan. Use when executing a documented plan queue such as todo/ or feat-name/ for a port, migration, or multi-stage feature.
confluence
Operational skill for Confluence: spaces, page trees, macros, labels, permissions, and REST content updates.
tpp
Work on a Technical Project Plan — read the plan, identify the current phase, do that phase's work, and update the plan with discoveries. Use when starting or resuming multi-session work tracked in a plan file.
handoff
Update the active Technical Project Plan for handoff when context is running low or the session is ending, so the next session continues instead of restarting.
github-project-setup
Set up a GitHub Project (v2) for a single repo or a multi-repo platform. Standardized statuses, custom fields (Tier or Initiative + Area/Priority/Effort/Mode), labels, and issue templates. Single-repo flow uses GitHub milestones; multi-repo flow uses a Project Initiative field for cross-repo coordination and surfaces…
to-issues
Break a plan, spec, or PRD into independently-grabbable issues on the GitHub Project using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.