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 joao-aires/agent-skills-public --skill project-conventionsgit clone --depth 1 https://github.com/joao-aires/agent-skills-publicWrote 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/joao-aires/agent-skills-public/project-conventions)<a href="https://agentmods.dev/skills/joao-aires/agent-skills-public/project-conventions"><img src="https://agentmods.dev/badge/skills/joao-aires/agent-skills-public/project-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/joao-aires/agent-skills-public/project-conventions"><img src="https://agentmods.dev/badge/skills/joao-aires/agent-skills-public/project-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.00058 | $0.02234 |
| Opus 5.5 | $0.00023 | $0.00894 |
| Sonnet 5.5 | $0.00012 | $0.00447 |
| Haiku 4.5 | $0.00006 | $0.00223 |
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 yesterday.
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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read workflow framing for skill selection and invocation boundaries.
Establish and maintain project conventions
Match the requested change
Read the request, existing code and accepted decisions before choosing structure.
- For a new project, establish a useful first slice. For an existing application, identify which foundation the requested change actually affects and update only that part; do not repeat setup or start a repository-wide reorganization during ordinary feature work.
- State the smallest useful user journey and its observable acceptance criteria; carry forward answers already agreed.
- Resolve ambiguity that changes the product or data boundary, and make reversible implementation choices without another planning ceremony.
- Use the conversation as scope unless a separate spec is useful; require no tickets or tracker.
Use system-design after product refinement and for consequential feature architecture before dependent planning/implementation. Derive platform, runtime and service choices from accepted requirements and operating constraints; reuse an existing stack and layout unless changing them solves an agreed problem. Add AI or a protocol interface for a concrete capability. Select matching technical guidance only when available; its installation is not acceptance of that technology.
Adopt an existing project and assess the change
Begin adoption by finding the repository's own route from checkout to running software. Read instructions and manifests, locate the startup/test/build/migration commands, and inspect the entry points those commands use. Trace a critical journey far enough to understand its service, data and identity dependencies. Check deployment definitions to understand the intended target, while keeping deployed state separate from repository intent.
Use that investigation to identify the conventions a contributor must preserve: component ownership, consumers, identity/tenant rules, configuration and operating constraints. Reuse existing instructions and add useful missing pointers. Installing the plugins grants no authority to restructure or modernize the application.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +33 lines ec62ee6254ea
- 2d ago Changed · -2 lines 363f6d411b44
- 3d ago Changed · -6 lines 58019b4e3b91
- 5d ago Changed · +19 lines 6afa89882226
- 7d ago Changed · +34 lines c8746ef0dfea
- 10d ago Changed · +6 lines 45d936a094ca
- 11d ago First seen · 42 lines · 58 tokens per session scan A f045ad6ac831
project-conventions is a skill published in the GitHub repository joao-aires/agent-skills-public (2 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 2,234 once invoked, about $0.0002 per session on Opus 5.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-10-11.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…