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 oborchers/fractional-cto --skill using-pedantic-principlesgit clone --depth 1 https://github.com/oborchers/fractional-ctoWrote 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/oborchers/fractional-cto/using-pedantic-principles)<a href="https://agentmods.dev/skills/oborchers/fractional-cto/using-pedantic-principles"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/using-pedantic-principles/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/oborchers/fractional-cto/using-pedantic-principles"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/using-pedantic-principles.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.00074 | $0.01058 |
| Opus 5.5 | $0.00030 | $0.00423 |
| Sonnet 5.5 | $0.00015 | $0.00212 |
| Haiku 4.5 | $0.00007 | $0.00106 |
Grade A, and why
using-pedantic-principles 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
These are not suggestions. They are non-negotiable standards for code that respects the reader. Your code works? Great. Now make it right.
How to Access Skills
Use the Skill tool to invoke any skill by name. When invoked, follow the skill's guidance directly.
Universal Principles
These apply to every language, every codebase, every commit.
| Skill | Triggers On |
|---|---|
pedantic-coder:naming-precision |
Variable names, function names, class names, file names, semantic accuracy, vague identifiers like data, temp, result, handle |
pedantic-coder:casing-law |
PascalCase, camelCase, snake_case, UPPER_SNAKE — mixed conventions, inconsistent casing across a codebase |
pedantic-coder:abbreviation-policy |
Shortened names, acronyms, inconsistent abbreviations (btn vs button, msg vs message), abbreviation rules |
pedantic-coder:boolean-naming |
Boolean variables, predicate functions, is/has/can/should prefixes, negative booleans, flag naming |
pedantic-coder:import-discipline |
Import statements, require calls, use declarations, import ordering, grouping, sorting, circular dependencies |
pedantic-coder:declaration-order |
File structure, member ordering in classes/structs, constant placement, export ordering, predictable file shape |
pedantic-coder:symmetry |
Parallel code paths, matching pairs (create/delete, open/close), consistent function signatures, structural mirroring |
pedantic-coder:one-pattern-one-way |
Inconsistent approaches to the same problem, mixed paradigms, local shortcuts that break codebase conventions |
pedantic-coder:magic-value-elimination |
Inline string literals, unexplained numbers, hardcoded values that should be named constants or enums |
pedantic-coder:dead-code-intolerance |
Commented-out code, unused imports, unreachable branches, TODO/FIXME comments, historical comments about removed code |
pedantic-coder:visual-rhythm |
Whitespace usage, blank line placement, consistent spacing between logical sections, code as prose |
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 · 72 lines · 74 tokens per session scan A 6cb7deaa9579
using-pedantic-principles is a skill published in the GitHub repository oborchers/fractional-cto (32 stars, last pushed 5d ago), licensed MIT. It adds 74 tokens to every session and 1,058 once invoked, about $0.0003 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-10-13.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…