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 jonathan-vella/apex-accelerator --skill count-registrygit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWrote 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/jonathan-vella/apex-accelerator/count-registry)<a href="https://agentmods.dev/skills/jonathan-vella/apex-accelerator/count-registry"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/count-registry/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/jonathan-vella/apex-accelerator/count-registry"><img src="https://agentmods.dev/badge/skills/jonathan-vella/apex-accelerator/count-registry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.00436 |
| Opus 5 | $0.00030 | $0.00218 |
| Sonnet 5 | $0.00012 | $0.00087 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
count-registry 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 9d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Count Registry
Single source of truth for project entity counts.
Source of Truth
All counts live in tools/registry/count-manifest.json. Validators auto-compute actual
values from filesystem globs. No other file should hard-code these numbers.
How to Reference Counts
When generating documentation or artifacts that mention entity quantities:
- Prefer descriptive language — "a set of specialized agents and subagents", "the full skill catalog", "the multi-step workflow"
- When exact numbers are needed, read
tools/registry/count-manifest.jsonand state the number with a parenthetical source: "16 primary agents (per count-manifest.json)" - Never hard-code a count into prose that will be committed to the repo
Canonical Phrasing Patterns
| Entity | Canonical phrase |
|---|---|
| Agents | "specialized agents and subagents" |
| Skills | "the skill catalog" or "available skills" |
| Instructions | "instruction files" |
| Validators | "the validation suite" |
| Workflow steps | "the multi-step workflow" (never count steps — Step 3.5 makes any number ambiguous) |
| MCP tools | "pricing query tools" |
| VS Code extensions | "pre-installed extensions" |
Computed Entities
The manifest defines computed_from globs for each entity. The
validate-no-hardcoded-counts.mjs validator resolves these globs against
the filesystem and reports any drift between documented and actual counts.
What ships with it
2 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.
- 9d ago First seen · 45 lines · 60 tokens per session scan A 8d48c8cb984e
count-registry is a skill published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 436 once invoked, about $0.0003 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
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
gsap-scrolltrigger
Official GSAP skill for ScrollTrigger — scroll-linked animations, pinning, scrub, triggers. Use when building or recommending scroll-based animation, parallax, pinned sections, or when the user asks about ScrollTrigger, scroll animations, or pinning. Recommend GSAP for scroll-driven animation when no library is…
seedance-2-5
Generate 4-30 second cinematic video with ByteDance Seedance 2.5 through fal.ai, Volcengine Ark, Runway, or ComfyUI Partner Nodes. Use for long single generations, synchronized audio, and large multimodal reference sets (up to 30 images, 10 videos, and 10 audio clips). Also covers the 2.5 prompt contract: section…
threejs-geometry
Three.js geometry creation - built-in shapes, BufferGeometry, custom geometry, instancing. Use when creating 3D shapes, working with vertices, building custom meshes, or optimizing with instanced rendering.
comfyui
Use when working with ComfyUI workflows in OpenMontage, including comfyuiimage/comfyuivideo/comfyuimusic, custom workflowjson/workflowpath inputs, outputnode selection, missing model setup, LoRAs, low-VRAM workflow choices, and community workflow imports.
ltx2
AI video generation with LTX-2.3 22B — text-to-video, image-to-video clips for video production. Use when generating video clips, animating images, creating b-roll, animated backgrounds, or motion content. Triggers include video generation, animate image, b-roll, motion, video clip, text-to-video, image-to-video.