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/robinfaraj/one-context/coding-stylenpx skills add robinfaraj/one-context --skill coding-stylegit clone --depth 1 https://github.com/robinfaraj/one-contextWhat 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 | $0.00019 | $0.00341 |
| Opus 5 | $0.00010 | $0.00170 |
| Sonnet 5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
coding-style 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 2d 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
OneContext Coding Style
Apply these conventions when writing or refactoring code in this monorepo.
Reference Files
| File | Scope |
|---|---|
coding-style.mdc |
General code quality — commenting, control flow, type derivation, business logic hygiene |
frontend.mdc |
React component patterns, composition, hooks, module organization |
backend.mdc |
Layered architecture, Hono route patterns, Zod validation, API design |
project-structure.mdc |
Monorepo layout, package descriptions, where to place new code |
Key Principles
- Self-documenting code — comment only to explain why, not what
- Early returns — flatten logic with guard clauses; avoid deep nesting
- Derive types from source — Prisma → Zod → API → frontend; avoid duplicate definitions
- Follow project structure — domain-first organization; place code where it belongs
- Biome for formatting — do not manually format; let the toolchain handle it
- Prefer Server Components — limit
use clientto interactive UI concerns - UI / visual: Apply brand-guidelines for colors, typography, spacing. Copy / messaging: Apply brand-copy-guidelines for headlines, CTAs, landing copy, docs, social (tone, voice, word choice).
What ships with it
4 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.
- 2d ago First seen · 31 lines · 19 tokens per session scan A 0324d2f877d6
coding-style is a skill published in the GitHub repository robinfaraj/one-context (43 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 341 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…