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/jimmypaolini/codebase/conformetry-configurenpx skills add JimmyPaolini/codebase --skill conformetry-configuregit clone --depth 1 https://github.com/JimmyPaolini/codebaseWrote 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/jimmypaolini/codebase/conformetry-configure)<a href="https://agentmods.dev/skills/jimmypaolini/codebase/conformetry-configure"><img src="https://agentmods.dev/badge/skills/jimmypaolini/codebase/conformetry-configure.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 | $0.00092 | $0.01800 |
| Opus 5 | $0.00046 | $0.00900 |
| Sonnet 5 | $0.00018 | $0.00360 |
| Haiku 4.5 | $0.00009 | $0.00180 |
Grade A, and why
conformetry-configure 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 3d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuring conformetry and writing templates
A generator pairs a name with a template — an ordinary folder of ordinary files — and the inputs needed to render it. The configuration declares generators; the template folder is the whole definition of what gets produced. The same template is then what instances are measured against, so a template is a standard as much as a starting point.
The configuration
The configuration file default-exports an array, one entry per generator. Only two fields are required:
| Field | Required | Meaning |
|---|---|---|
name |
yes | How the generator is invoked |
templatePath |
yes | Template folder, relative to the workspace root |
inputs |
no | Values the template renders with, as JSON Schema fragments |
instances |
no | Where this generator's output already lives |
aliases |
no | Short alternative names |
description |
no | Shown when generators are listed |
threshold |
no | Lowest conformance score this generator's instances may have, 0 to 1 |
Unknown keys are stripped silently rather than rejected, so a misspelled field is not an error — it simply does nothing. Check your entry took effect by listing the generators:
conformetry templates
A generator with neither inputs nor instances is legal: it renders a fixed
template that nothing validates afterwards.
Three collisions the configuration refuses to load with
- Names and aliases share one namespace. An alias may not collide with another generator's name, or with another alias.
- Two generators may not name the same
templatePath. Validation could not tell which generator a matching instance belongs to. - A name or alias may not be empty or contain a path separator. Each becomes a filename in the emitted Nx plugin.
Instance groups: where output already lives
instances is a list of groups, each with optional patterns, tags,
substitutions, and threshold. Groups exist so substitutions — and the
conformance bar — can differ per set of paths.
What ships with it
1 file 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.
- 3d ago First seen · 186 lines · 92 tokens per session scan A 5498da45c59c
conformetry-configure is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 1,800 once invoked, about $0.0005 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-09-01.
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.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…