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 martian56/claude-engineer --skill project-conventionsgit clone --depth 1 https://github.com/martian56/claude-engineerWrote 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/martian56/claude-engineer/project-conventions)<a href="https://agentmods.dev/skills/martian56/claude-engineer/project-conventions"><img src="https://agentmods.dev/badge/skills/martian56/claude-engineer/project-conventions.svg" alt="Measured on agentmods" 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.00061 | $0.00646 |
| Opus 5 | $0.00030 | $0.00323 |
| Sonnet 5 | $0.00012 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
project-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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Conventions
Announce at start: "I'm using claude-engineer:project-conventions to set up the repo's house style."
Folder contract
_private/- UNCOMMITTED working area: drafts, screenshots, scratch notes, research. Add to.gitignore.docs/- COMMITTED non-code:docs/plan/*(the plan),docs/decisions.md, architecture, runbooks, API docs..claude-engineer/- durable state (seeclaude-engineer:project-memory). Commitmemory.md/progress.md; ignorequality-gate-status.json.- code - the monorepo (
apps/,packages/,services/,libs/; seeclaude-engineer:monorepo-and-tooling).
Phase 0 setup (create a task per item)
git init(if not a repo). Create.gitignorecovering_private/,.claude-engineer/quality-gate-status.json,node_modules,.venv, build dirs,.env*.- Create
_private/anddocs/(withdocs/plan/). - Generate a root
CLAUDE.mdcapturing: the stack, the iron laws (plan-gated, CX-first, services-in-docker/app-native, the four quality gates), how to run things, and where state lives. This is the project's standing instruction file. - Initialize the conventions registry at
docs/conventions.md- the house style the agent must reuse instead of reinventing: naming, error handling, API response shape, folder patterns, and a UI pattern registry (component + token usage; generalize the design system's DESIGN.md into reusable patterns). Append to it whenever a new pattern is established. - Write
docs/recommended-mcps.mdfromtemplates/recommended-mcps.mdand tell the user which MCPs to install with their own keys.
MCP policy (BYO keys)
Claude-Engineer references MCP servers; it never bundles secrets. Users install with their own keys via each provider's command. See templates/recommended-mcps.md for Playwright, Chrome DevTools, 21st.dev Magic, and designmd (getdesign.md).
Red flags - STOP
- Committing screenshots/scratch to git → those belong in
_private/. - Inventing a new pattern that contradicts
docs/conventions.md→ reuse the house style or update the registry deliberately. - Secrets or API keys written into committed files → never; use
.env*(git-ignored) and document required vars.
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 · 30 lines · 61 tokens per session scan A 070b08a12aba
project-conventions is a skill published in the GitHub repository martian56/claude-engineer (2 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 646 once invoked, about $0.0003 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
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
team-topologies
Organize business and technology teams for fast flow using Skelton & Pais's "Team Topologies". Use when the user mentions "team topologies", "Conway's law", "platform team", "stream-aligned team", "team boundaries", "cognitive load", "how should we split teams", "who owns this service", "team dependencies", or…
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
chief-information-officer
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost…