Borrowing it
Nothing to install: this file belongs to jmanhype/speckit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jmanhype/speckit/main/.claude/skills/project-standards/SKILL.mdgit clone --depth 1 https://github.com/jmanhype/speckitWrote 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/jmanhype/speckit/project-standards)<a href="https://agentmods.dev/skills/jmanhype/speckit/project-standards"><img src="https://agentmods.dev/badge/skills/jmanhype/speckit/project-standards/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/jmanhype/speckit/project-standards"><img src="https://agentmods.dev/badge/skills/jmanhype/speckit/project-standards.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.00041 | $0.00815 |
| Opus 5.5 | $0.00016 | $0.00326 |
| Sonnet 5.5 | $0.00008 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
project-standards 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Standards Skill
You are implementing code in a project that follows specific architectural principles and coding standards defined in the project constitution.
When to Invoke This Skill
Claude should use this skill when:
- Writing or modifying code
- Making architectural decisions
- Implementing tasks from tasks.md
- Reviewing code for compliance
- Setting up new components or services
How to Use
-
Read the constitution to understand project principles:
Read: .specify/memory/constitution.md -
Apply principles during implementation:
- TDD: Write tests first, ensure they fail, then implement
- SOLID: Follow single responsibility, dependency injection
- Security: No hardcoded secrets, validate all inputs
- Observability: Add logging, metrics, tracing
-
Check compliance before marking tasks complete
Key Principles Summary
Test-Driven Development (TDD)
- Write tests BEFORE implementation code
- Tests must FAIL initially (Red phase)
- Implement to make tests pass (Green phase)
- Refactor after passing (Refactor phase)
- 100% test pass rate required (enforced by test-gate.sh)
SOLID Architecture
- Single Responsibility: One reason to change per class/module
- Open/Closed: Extend via interfaces, don't modify
- Liskov Substitution: Implementations substitutable for abstractions
- Interface Segregation: Many focused interfaces
- Dependency Inversion: Depend on abstractions, inject implementations
Security-First
- Secrets in environment variables or secret managers only
- Input validation with strict schemas (Pydantic, Zod)
- Parameterized queries only (no string interpolation for SQL)
- Row-Level Security (RLS) for multi-tenant data
- Rate limiting on all API endpoints
Code Quality
- Type hints/annotations required
- Linting must pass (ruff, ESLint)
- Docstrings for public APIs
- Meaningful variable/function names
Observability
- Structured JSON logging with correlation IDs
- Health check endpoints (/health, /ready, /live)
- Metrics for critical operations
- Distributed tracing for cross-service calls
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 · 120 lines · 41 tokens per session scan A 43d2bbc5691d
project-standards is a skill published in the GitHub repository jmanhype/speckit (26 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 815 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-09-01.
Other skills, from other repositories
confidence-based-strictness
Use when the complexity or unfamiliarity of a task should increase guardrail enforcement. Scales verification depth based on how confident the system is in the correctness of the generated code.
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
software-code-refactoring
Improve production code quality while preserving all existing test behavior. Commonly used for the Refactor phase of TDD red-green-refactor, but applicable to any codebase with tests. Use when production code works but needs cleanup — reducing duplication, improving naming, simplifying complexity, aligning with…
ring:running-dev-cycle
Running the backend dev cycle: implements every task in a rolling-wave plan.md (ring:writing-plans format) for a Go/TS service, driving specialist agents through Gate 0 implementation/TDD, Gate 8 parallel review, and Gate 9 validation per epic, elaborating later phases at each phase boundary. Use when starting or…
ring:instrumenting-streaming-events
Instrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated…
gentle-ai
Use Gentle AI harness discipline for Pi work: clarify first, preserve OpenSpec artifacts, use strict TDD where available, delegate through subagents when useful, and protect review workload.