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.
git 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/plugins/big-emotion/agent-atelier/project-standard)<a href="https://agentmods.dev/plugins/big-emotion/agent-atelier/project-standard"><img src="https://agentmods.dev/badge/plugins/big-emotion/agent-atelier/project-standard/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/plugins/big-emotion/agent-atelier/project-standard"><img src="https://agentmods.dev/badge/plugins/big-emotion/agent-atelier/project-standard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
project-standard 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 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.
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.
What it actually says
{
"name": "project-standard",
"displayName": "Big Emotion Project Standard",
"version": "0.2.0",
"description": "Installs and configures the Big Emotion project standard on any repo: CI quality gates, Husky hooks, the four project skills, Atlassian wiring, and Ferry.",
"author": {
"name": "Big Emotion"
},
"homepage": "https://github.com/big-emotion/agent-atelier",
"repository": "https://github.com/big-emotion/agent-atelier",
"license": "MIT",
"keywords": ["standards", "scaffolding", "ci", "husky", "ferry", "atlassian"]
}
What it installs
The manifest is a name and a version. 6 skills travel with it, and installing the plugin installs all of them — 125 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 14 lines scan A 311ba5c67ad7
project-standard is a plugin published in the GitHub repository big-emotion/agent-atelier (3 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
handbook-glab
GitLab CLI (glab) expertise for managing merge requests, issues, CI/CD pipelines, and repositories from the command line.
npm-toolkit
A toolkit for publishing npm packages and configuring GitHub Actions, the automation service built into GitHub. It covers OIDC trusted publishing, release automation choices, and workflow configuration.
privacy-guard
Keeps private infrastructure details out of public repositories. Ships the privacy-guard skill: session rules for what must never cross the public boundary, plus a per-repo pre-commit gate built on a gitignored local denylist and gitleaks. The denylist is never committed, so the hook is a no-op for external…
github-workflow
Git commit, PR creation, review, and merge skills following Conventional Commits.
nyann
Project governance for Claude Code. Bootstrap and maintain git workflow, hooks, commits, releases, CI, docs, and repo health.
coding
Opinionated Claude Code workflow skills: clear and unambiguous technical writing (write-clearly), iterative planning (replan), proof-based code review (review, review-staged, second-opinion), disciplined Conventional-Commit staging (gitplan, stage), finding the session that wrote an uncommitted change (find), and the…