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 Primadetaautomation/primadata-marketplace --skill production-code-standardsgit clone --depth 1 https://github.com/Primadetaautomation/primadata-marketplaceWrote 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/primadetaautomation/primadata-marketplace/production-code-standards)<a href="https://agentmods.dev/skills/primadetaautomation/primadata-marketplace/production-code-standards"><img src="https://agentmods.dev/badge/skills/primadetaautomation/primadata-marketplace/production-code-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/primadetaautomation/primadata-marketplace/production-code-standards"><img src="https://agentmods.dev/badge/skills/primadetaautomation/primadata-marketplace/production-code-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.00024 | $0.01779 |
| Opus 5 | $0.00012 | $0.00890 |
| Sonnet 5 | $0.00005 | $0.00356 |
| Haiku 4.5 | $0.00002 | $0.00178 |
Grade A, and why
production-code-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 10d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Code Standards Skill
Overview
This skill encapsulates the CLAUDE Framework standards for production-ready code development. It ensures consistency, quality, security, and maintainability across all code deliverables.
When to Use This Skill
- Creating new features requiring production quality
- Code reviews against production standards
- Refactoring legacy code to modern standards
- Training on development best practices
- Pre-deployment quality validation
Core Principles (Level 1 - Always Loaded)
🎯 Priority Rules (CRITICAL - Non-Negotiable)
Basis Missie - Breaking these = delivery rejected:
- BM-1 (MUST): Never invent, omit, or skip functionality
- BM-2 (MUST): Follow exact instructions from user
- BM-3 (MUST): Ask questions when unclear, never assume
Impact Analysis - Before ANY code change:
- IA-1 (MUST): Analyze impact on existing functionality
- IA-2 (MUST): Check all dependencies that will be affected
- IA-3 (MUST): Search for all files that import/use the code
- IA-4 (MUST): Run existing tests BEFORE changes
- IA-5 (MUST): Backup/document original implementation when overwriting
- IA-6 (MUST NOT): Never overwrite code without impact check
- IA-7 (MUST): Ask permission before overwriting with impact explanation
🔴 Code Quality Standards
Single Responsibility & DRY:
// ✅ GOOD - Single responsibility
class UserAuthenticator {
authenticate(credentials: Credentials): AuthResult {
return this.validateAndAuthenticate(credentials);
}
}
class UserNotifier {
sendWelcomeEmail(user: User): void {
this.emailService.send(user.email, 'Welcome!');
}
}
// ❌ BAD - Multiple responsibilities
class UserManager {
authenticate() { /* auth logic */ }
sendEmail() { /* email logic */ }
updateDatabase() { /* db logic */ }
}
Naming Conventions (MUST):
- Functions:
getUserData(),calculateTotal()(verbs) - Variables:
user,totalAmount(nouns) - Booleans:
isValid,hasPermission(is/has prefix) - Constants:
MAX_RETRY_COUNT,API_BASE_URL - Classes:
UserService,OrderController(PascalCase)
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.
- 10d ago First seen · 255 lines · 24 tokens per session scan A ab30a5584062
production-code-standards is a skill published in the GitHub repository Primadetaautomation/primadata-marketplace (5 stars, last pushed 9mo ago), licensed MIT. It adds 24 tokens to every session and 1,779 once invoked, about $0.0001 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
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.