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 project-standard-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/project-standard-spec)<a href="https://agentmods.dev/skills/big-emotion/agent-atelier/project-standard-spec"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/project-standard-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/project-standard-spec"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/project-standard-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.00105 | $0.05704 |
| Opus 5 | $0.00053 | $0.02852 |
| Sonnet 5 | $0.00021 | $0.01141 |
| Haiku 4.5 | $0.00011 | $0.00570 |
Grade A, and why
project-standard-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- {{project_slug}}-spec — 92% identical, 47 lines differ
How it starts
The opening of the file, as written. The whole thing — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Big Emotion Project Standard Spec
M4 wiring pending for this repo — preconditions below will fail-fast until a Jira project + Confluence space are bootstrapped (run
/project-standard:setupmodule M4, thenproject-standard-bootstrap-confluence).
Maintain the Big Emotion Project Standard 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 the project whose key is jiraProjectKey in docs/confluence-spec/config.json, 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-standard-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-standard-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-standard-bootstrap-confluenceand runs only once.
- The user pastes a Jira ticket URL or key — that path belongs to
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 · 307 lines · 105 tokens per session scan A 95f2c12f18b3
project-standard-spec is a skill published in the GitHub repository big-emotion/agent-atelier (2 stars, last pushed 3d ago), licensed MIT. It adds 105 tokens to every session and 5,704 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-31.
Other skills, from other repositories
add-azuredevops
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
azure-devops
Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check…
repo-health-triage
Use when a scheduled or watcher tick requests a repository-health pass. Not for source, label, merge, or close mutation.
ccc-broadcast
Relay CC Commander build, deploy, CI, task, and cost signals to your team's chat or email so non-devs see what shipped — read-only, no secrets in payloads.
scheduler
Manage scheduled jobs — create, update, list, run remote agents on cron. Use when setting up recurring tasks, checking job status, or managing automation.
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.