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 auditgit 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/audit)<a href="https://agentmods.dev/skills/big-emotion/agent-atelier/audit"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/audit/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/audit"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/audit.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.02759 |
| Opus 5.5 | $0.00000 | $0.01104 |
| Sonnet 5.5 | $0.00000 | $0.00552 |
| Haiku 4.5 | $0.00000 | $0.00276 |
Grade C, and why
{{project_slug}}-audit 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: append the project-type domains that make this audit meaningful — typically 2 to 4 more rows. Examples from reference repos: a public website added "RGPD / privacy", "RGAA / accessibility", "Perfor How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{project_display_name}} Audit
Read-only audit of the project defined in this repo. Produces a scored, evidence-based report and refreshes docs/PRODUCTION-READINESS-AUDIT.md.
This skill never modifies source, never bumps versions, never tags, never pushes, never deploys, never writes to external services. It only reads, runs the repo's own gates, and writes the audit doc. Fixing anything it finds is deferred to normal ticketed work or /{{project_slug}}-release.
When to Activate
- User asks: "is the project production-ready", "is it ready to ship", "audit {{project_slug}}", "score the project".
- User asks specifically about security posture, compliance, or overall score.
- User invokes
/{{project_slug}}-audit.
Preconditions
Run from the repo root (package.json with "name": "{{project_slug}}"). If not, stop and tell the user to cd into the repo.
Inputs
Optional argument: --quick — skip the long/costly gates (full test suite, production build, any gate that hits a paid external API). Rely instead on the most recent CI run (gh run list --workflow ci.yml) and the newest local artifacts, and mark any domain scored from stale data as such.
Default: full audit.
Workflow
Step 1 — Snapshot the repo state
Run in parallel via Bash:
git status --porcelain— a dirty tree is auditable but must be reported.git log --oneline -15— recent cadence.git tag --sort=-creatordate | head -5— no tags yet is expected pre-launch; say so explicitly.jq '{name, version, private, packageManager, scripts}' package.json— version, scripts, package manager.ls .github/workflows/— workflow surface.ls docs/— structural map.
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 · 170 lines · 0 tokens per session scan C 63ad029e4ae8
{{project_slug}}-audit is a skill published in the GitHub repository big-emotion/agent-atelier (3 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,759 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
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.
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
ci-fixer
A CI job fails on a named revision and the fix belongs in code, config or tests, not in the CI provider.
cloudflare-workers-ci-cd
Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI. Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues.
bun-sveltekit
Use when building or running SvelteKit apps on Bun, including SSR, adapters, and Bun-specific APIs.
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).