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 agentmods add skills/mrkt365-india/boilerforge/coding-standardsnpx skills add MRKT365-India/boilerforge --skill coding-standardsgit clone --depth 1 https://github.com/MRKT365-India/boilerforgeWrote 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/mrkt365-india/boilerforge/coding-standards)<a href="https://agentmods.dev/skills/mrkt365-india/boilerforge/coding-standards"><img src="https://agentmods.dev/badge/skills/mrkt365-india/boilerforge/coding-standards.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.00000 | $0.00031 |
| Opus 5 | $0.00000 | $0.00015 |
| Sonnet 5 | $0.00000 | $0.00006 |
| Haiku 4.5 | $0.00000 | $0.00003 |
Grade A, and why
coding-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 4d 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.
What it actually says
coding-standards
Follow the project's coding standards:
- Keep functions small and readable.
- Prefer explicit naming.
- Add tests for behavior changes.
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.
- 4d ago First seen · 7 lines · 0 tokens per session scan A a9b083c7fd4e
coding-standards is a skill published in the GitHub repository MRKT365-India/boilerforge (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 31 tokens. 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
spec-harness-generate-agents
Bind the 6 SDD agents to THIS project's rules — fill each agent's GEN:rules region with its concern's real rules (implementer←Coding, tester←Testing+commands, reviewer←Reviewing, researcher/planner←Architecture, verifier←goal). Use when Malik says 'generate the agents', 'make the agents project-specific', 'bind agents…
spec-harness-audit
Health-check the memory bank, rules, and index — flag stale, contradictory, or redundant entries and spec↔code drift. Use when Malik says 'audit the bank', 'is the memory stale', 'check spec harness health', or 'clean up the rules'.
spec-harness-build
Run the SDD pipeline over tasks.md: implement → test → VERIFY → review, one task at a time, under the ratchet. Use when Malik says 'build it', 'run the pipeline', 'implement the tasks', or 'ship this feature'. Each task gated by the separate verifier; lessons harvested by learn.
spec-harness-install
Add or refresh Spec Harness in a repo — greenfield (new) or existing (integrate), idempotent. Use when Malik says 'install spec harness', 'set this repo up with spec harness', 'integrate spec harness into X', or 'start a new spec-harness project'. Runs the interview (mode, stack, constraints, work-intake source…
spec-harness-learn
The learning loop — turn feedback, a correction, or a verifier-FAIL root cause into one enforced rule injected into the ratchet (AGENTS.md/airules), dated. Use when Malik says 'learn this', 'remember not to do X', 'capture this lesson', 'don't do that again', or right after he corrects you. Closes the loop the…
spec-harness-rules
Per-directory rules — resolve the nearest RULES.md for a path (coding/architecture/packages/testing/reviewing), or generate it from a directory's real code when missing. Use when Malik says 'different directories have different rules', 'add rules per directory', 'each package needs its own rules', 'what rules apply…