Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add toBzh30/Claude-Project-Bootstrap/plugin install claude-project-bootstrapWrote 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/tobzh30/claude-project-bootstrap/update-conventions)<a href="https://agentmods.dev/skills/tobzh30/claude-project-bootstrap/update-conventions"><img src="https://agentmods.dev/badge/skills/tobzh30/claude-project-bootstrap/update-conventions/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/tobzh30/claude-project-bootstrap/update-conventions"><img src="https://agentmods.dev/badge/skills/tobzh30/claude-project-bootstrap/update-conventions.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.00142 | $0.03201 |
| Opus 5 | $0.00071 | $0.01600 |
| Sonnet 5 | $0.00028 | $0.00640 |
| Haiku 4.5 | $0.00014 | $0.00320 |
Grade A, and why
update-conventions 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/update-conventions — Pull plugin-template improvements into this repo
The plugin's hooks, skills, and commands auto-trickle when you update the marketplace — they run from the plugin install. But two things don't reach an already-bootstrapped repo on their own: (1) the files this plugin copied into the repo at bootstrap (working-agreements.md, the issue templates) are owned by the repo from that moment on, so template improvements never reach them; and (2) a plugin added to the marketplace after this repo was bootstrapped (e.g. engineering-craft) is never switched on here — and a plugin's skills only trickle in once it's in enabledPlugins. This skill closes both gaps on demand.
Direction: one-way, template → repo (pull-down only). It surfaces what the bundled template grew and offers to merge it in. It never overwrites your local customizations, and it never pushes repo changes back up to the plugin — a repo that has improved its own conventions and wants to contribute that upstream does so via a normal PR to the plugin repo, not through this skill.
Scope — only the shared-convention files:
| File (in this repo) | Bundled template | Reconciled? |
|---|---|---|
.claude/rules/working-agreements.md |
bootstrap-working-agreements/templates/working-agreements.md |
Yes — primary |
.github/ISSUE_TEMPLATE/feature.yml |
github-project-setup/templates/feature.yml |
Yes |
.github/ISSUE_TEMPLATE/bug.yml |
github-project-setup/templates/bug.yml |
Yes |
.claude/settings.json (enabledPlugins) |
bootstrap-working-agreements Step 6.5 |
Yes — retrofit missing plugin enablements (e.g. engineering-craft) |
.claude/gh-project.json (siblings) |
github-project-setup Step 4b |
Yes — retrofit the opt-in sibling-status hook flag (multi-repo, side-by-side setups) |
Deliberately out of scope (a diff would be all noise — these are per-repo content, not shared convention): the root/spoke CLAUDE.md scaffolds, .claude/rules/roadmap.md, and the body of .claude/rules/decisions.md.
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.
- 8d ago First seen · 194 lines · 142 tokens per session scan A d821d02066cb
update-conventions is a skill published in the GitHub repository toBzh30/Claude-Project-Bootstrap (3 stars, last pushed 1mo ago), licensed MIT. It adds 142 tokens to every session and 3,201 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
project-standard-spec
Spec maintainer for Big Emotion Project Standard. Reads Confluence (Requirements / Decisions / Architecture) as the source of truth, helps you investigate a problem, structures the reflection, and produces drafts — Pending REQ/DEC/ARCH sections on Confluence + matching Jira tickets in the Jira project configured in…
fix-ci-train
Batch-fix the CI on every open pull request whose required checks are red — CI only, no review, no merge. From a GitHub PRs URL (or the current repo), enumerate every open PR with failing required checks, fetch each PR's failing-check logs, consolidate a per-PR CI-fix checklist, dispatch a team of parallel fixer…
issue-train
Batch-process every open GitHub issue in a list — triage, detect existing PR linkage, detect silent fixes in already-merged PRs, close issues that are no longer pertinent, then plan + build + open one PR per remaining actionable issue with Closes.
blueprint
Extract a complete specs/ directory from any frontend codebase. Covers all 12 axes needed to rebuild or migrate a frontend app. Produces 80% quality on first pass, refined to 95% through guided iteration.
fix-train
Batch-apply the requested changes on every open pull request in a GitHub list — fix only, no merge. From a GitHub PRs URL (or the current repo), enumerate every open PR, collect each PR's requested changes (formal CHANGESREQUESTED reviews, inline review comments, and "Issues requiring changes" comments /…
project-standard-audit
Production-readiness audit for Big Emotion Project Standard (this repo). Read-only multi-domain scored assessment that answers four questions — is the plugin ready to install on real repos, is the template surface healthy, what is the security posture, and is the score close to 8–9/10. Use when the user asks "is it…