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/codometer-configurenpx skills add JimmyPaolini/codebase --skill codometer-configuregit clone --depth 1 https://github.com/JimmyPaolini/codebaseWhat 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.00097 | $0.02372 |
| Opus 5 | $0.00048 | $0.01186 |
| Sonnet 5 | $0.00019 | $0.00474 |
| Haiku 4.5 | $0.00010 | $0.00237 |
Grade A, and why
codometer-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 today.
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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing a codometer configuration
codometer.config.{ts,mts,cts,js,mjs,cjs,json,jsonc} is read from the directory
being measured, or from any directory above it — the search walks upward and
takes the first file found. The nearest configuration wins outright, and is
never merged with one further up: a merged limit that never applied to this
folder would look exactly like one that did. Every field is optional; a
repository with none of these files is measured with the defaults.
import { type CodometerConfiguration } from "@codometer/configuration";
const codometerConfiguration: CodometerConfiguration = {
exclude: ["notepads/**"],
excludeFrom: ["configuration/.codometerignore"],
defaultTarget: "codebase",
limits: [{ metric: "typescript.interfaces", severity: "warn", value: 500 }],
targets: [
{
analyses: ["size"],
include: ["dist/**/*.js", "!dist/**/*.map.js"],
name: "compiled",
},
],
output: { markdown: { path: "README.md" } },
};
export default codometerConfiguration;
Output paths resolve relative to the directory being measured, not to the
configuration file, so a configuration kept in a configuration/ folder still
writes to the project root it describes.
One configuration for every folder in a workspace
Export a function instead of an object to let one file at the top of a workspace describe every project beneath it:
import path from "node:path";
import {
type CodometerConfiguration,
type CodometerConfigurationFactory,
} from "@codometer/configuration";
const codometerConfiguration: CodometerConfigurationFactory = (context) => {
const projectPath = path.relative(
context.configurationDirectory,
context.directory,
);
return {
targets: [
{
analyses: ["size"],
directory: path.relative(context.directory, context.configurationDirectory),
include: [`dist/${projectPath}/**/*.js`],
name: "compiled",
},
],
} satisfies CodometerConfiguration;
};
export default codometerConfiguration;
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.
- today First seen · 230 lines · 97 tokens per session scan A 077c8dd9564a
codometer-configure is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 2,372 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…