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 releasegit 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/release)<a href="https://agentmods.dev/skills/big-emotion/agent-atelier/release"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/release/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/release"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/release.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.00000 | $0.02778 |
| Opus 5.5 | $0.00000 | $0.01111 |
| Sonnet 5.5 | $0.00000 | $0.00556 |
| Haiku 4.5 | $0.00000 | $0.00278 |
Grade C, and why
{{project_slug}}-release scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- PROJECT-SPECIFIC: list the deploy workflow's steps in the post-push message (build, deploy target, GitHub Release creation, deployment annotations, conditional re-syncs). If the workflow creates the GitHub Release i How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{project_display_name}} Release
Prepare a release locally (bump version, update CHANGELOG, create the commit and tag), then ask for explicit confirmation before pushing.
This skill writes to the local repo first. It only runs git push after the user explicitly confirms. Without confirmation, the commit + tag stay local.
When to Activate
- User says: "release {{project_slug}}", "cut a release", "bump version", "tag a new version", "ship a release".
- User invokes
/{{project_slug}}-release(optionally with a bump level:patch | minor | major | <explicit-version>).
Preconditions
Verify all of the following before any write. If any fail, do not modify anything — report the blocker and exit.
- In the repo root —
package.jsonhas"name": "{{project_slug}}". If not, stop and tell the user tocdto the right directory. - Clean working tree —
git status --porcelainmust be empty. If dirty, stop and ask the user to commit or stash. - On
{{default_branch}}branch —git branch --show-currentmust return{{default_branch}}. If not, stop. Releases ship from{{default_branch}}only; feature work lands on{{integration_branch}}first (Ferry branch model). - Up to date with
origin/{{default_branch}}— rungit fetch originthengit rev-list --count {{default_branch}}..origin/{{default_branch}}. If > 0, stop and tell the user togit pull. - CI green on HEAD — run:
The latest run must haveHEAD_SHA=$(git rev-parse HEAD) gh run list --repo {{github_org}}/{{github_repo}} \ --commit "$HEAD_SHA" --workflow ci.yml \ --limit 1 --json conclusion,status,urlconclusion: "success". If no run exists for HEAD, or the conclusion is notsuccess, stop and provide the run URL so the user can investigate.
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 · 249 lines · 0 tokens per session scan C f43de67b7c29
{{project_slug}}-release is a skill published in the GitHub repository big-emotion/agent-atelier (3 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,778 tokens. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other skills, from other repositories
ops-ship
OPS on-demand: This skill should be used when the user asks to "ship ops plugin", "merge all PRs and…
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
pipeline-digest
Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, and which branches went stale, and notifies the operator only when that state actually moved since the last run. Use when the operator asks "what moved in the pipeline", "anything to ship"…
npm-publish
A setup guide for automatically publishing an npm package through GitHub Actions to npmjs.com. npmjs.com is a registry where JavaScript packages are shared, and GitHub Actions runs automated tasks from a repository.
wicked-garden-platform-gh-cli
Use when you need gh CLI patterns beyond the basics — debugging failed workflow runs, bulk PR operations, release automation, or repo health checks. Provides composable gh invocations for power users. NOT for simple git commands (use Bash) or GitLab (use the glab-cli skill). Use when: "debug the failed workflow run"…
wicked-garden-platform-glab-cli
Use when you need glab CLI patterns for GitLab — pipeline debugging, MR management, or release automation. Provides composable glab invocations for power users. NOT for GitHub (use the gh-cli skill) or simple git commands (use Bash).