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/jhlee0409/omni-harness-kit/coding-guidelinesnpx skills add jhlee0409/omni-harness-kit --skill coding-guidelinesgit clone --depth 1 https://github.com/jhlee0409/omni-harness-kitWrote 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/jhlee0409/omni-harness-kit/coding-guidelines)<a href="https://agentmods.dev/skills/jhlee0409/omni-harness-kit/coding-guidelines"><img src="https://agentmods.dev/badge/skills/jhlee0409/omni-harness-kit/coding-guidelines.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.00075 | $0.00350 |
| Opus 5 | $0.00037 | $0.00175 |
| Sonnet 5 | $0.00015 | $0.00070 |
| Haiku 4.5 | $0.00007 | $0.00035 |
Grade A, and why
coding-guidelines 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 5d 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 guidelines
Apply while writing or changing code — these counter the usual LLM failure modes.
- Surgical changes. Change the minimum to achieve the goal. Don't rewrite working code you were only asked to extend; don't reformat unrelated lines.
- Don't overcomplicate. Prefer the simplest thing that works — no speculative abstraction, no config for a case that doesn't exist yet. Delete before you add.
- Match the surroundings. New code reads like the code around it — naming, idioms, comment density, error handling. Don't import a foreign style.
- Surface assumptions. If the task hinges on an unstated assumption (a field exists, an API behaves a certain way), state it and verify it (grep / run) before building on it.
- Verifiable success. Before starting, name how you'll KNOW it works (a test, a command, an observable output). "Done" means that check actually ran and passed.
- No silent scope creep. Do what was asked; if you spot adjacent work, surface it — don't fold it in unannounced.
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.
- 5d ago First seen · 28 lines · 75 tokens per session scan A f877fcee733d
coding-guidelines is a skill published in the GitHub repository jhlee0409/omni-harness-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 350 once invoked, about $0.0004 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
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
ops-pocket
OPS on-demand: This skill should be used when the user asks to "pocket memos", "voice memo pipeline"…
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.