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-ticketgit 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-ticket)<a href="https://agentmods.dev/skills/big-emotion/agent-atelier/project-standard-ticket"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/project-standard-ticket/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-ticket"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/project-standard-ticket.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.00143 | $0.03603 |
| Opus 5 | $0.00072 | $0.01801 |
| Sonnet 5 | $0.00029 | $0.00721 |
| Haiku 4.5 | $0.00014 | $0.00360 |
Grade A, and why
project-standard-ticket 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 12d 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}}-ticket — 86% identical, 76 lines differ
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Big Emotion Project Standard Ticket
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). This repo also has noferry.config.jsonyet (M5), which precondition 5 requires.
Take a single Jira ticket from link to merged-ready PR, locally and unattended.
This is the local, interactive, on-demand counterpart to Ferry (which runs the same lifecycle async/cloud via Jira Automation). It does not call Ferry; it does the work directly on the developer's machine. To avoid divergence with Ferry, the base branch, the PR target branch, and the review column are read from ferry.config.json at runtime — never hard-coded. The one deliberate divergence is the working-branch prefix: the config's working_branch_prefix names the namespace Ferry's automation owns (typically ferry/), so local runs stay out of it and use the human-style prefixes of the repo history instead (feat/, fix/ — Step 5).
Operating mode — FULL AUTO
The user chose no confirmation gates. The skill runs the entire chain — assign → read → refine → sub-tasks → branch → implement → PR → Jira transition + comment — without stopping to ask.
"Full auto" removes confirmation prompts. It does not remove safety blockers: a small set of hard preconditions where proceeding would corrupt shared state or produce a broken PR. On a safety blocker the skill stops and reports — it does not guess or force through. These are listed under Preconditions and are non-negotiable.
When to Activate
- User pastes a Jira ticket URL (e.g.
https://<org>.atlassian.net/browse/KEY-123) or a bare issue key. - User says: "prends ce ticket", "implémente / traite ce ticket Jira", "fais ce ticket".
- User invokes
/project-standard-ticket <jira-url-or-key>.
Inputs
A single argument: the Jira ticket URL or issue key.
- Accept
.../browse/KEY-123,...selectedIssue=KEY-123,...?...&issueKey=KEY-123, or a bareKEY-123. - Extract the issue key with the regex
[A-Z][A-Z0-9]+-\d+. If zero or more than one distinct key is found, stop and ask the user for the exact key (ambiguous input is a safety blocker, not a design choice).
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.
- 12d ago First seen · 181 lines · 143 tokens per session scan A e1b0b0405766
project-standard-ticket is a skill published in the GitHub repository big-emotion/agent-atelier (2 stars, last pushed 4d ago), licensed MIT. It adds 143 tokens to every session and 3,603 once invoked, about $0.0007 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.