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/vohongtho/code-intel-platform/fixturesnpx skills add vohongtho/code-intel-platform --skill fixturesgit clone --depth 1 https://github.com/vohongtho/code-intel-platformWhat 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.00048 | $0.01208 |
| Opus 5 | $0.00024 | $0.00604 |
| Sonnet 5 | $0.00010 | $0.00242 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
fixtures 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 yesterday.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fixtures
75 symbols | 10 files | path:
code-intel/core/tests/parser-corpus/fixtures/| call density: 0/sym
When to Use
Load this skill when:
- The task involves code in
code-intel/core/tests/parser-corpus/fixtures/ - The user mentions
server_init,server_start,internal_calcor asks how they work - Adding, modifying, or debugging fixtures-related functionality
- Tracing call chains that pass through the fixtures layer
Key Files
| File | Symbols | Notes |
|---|---|---|
code-intel/core/tests/parser-corpus/fixtures/php-sample.php |
UserService, __construct, getUser, saveUser +(6) |
10 exported |
code-intel/core/tests/parser-corpus/fixtures/csharp-sample.cs |
UserService, GetUser, SaveUser, FormatName +(5) |
5 exported |
code-intel/core/tests/parser-corpus/fixtures/rust-sample.rs |
Server, Config, ServerError, Handler +(5) |
internal |
code-intel/core/tests/parser-corpus/fixtures/java-sample.java |
UserService, getUser, saveUser, formatName +(4) |
5 exported |
code-intel/core/tests/parser-corpus/fixtures/go-sample.go |
Server, Config, Handler, New +(3) |
6 exported |
code-intel/core/tests/parser-corpus/fixtures/python-sample.py |
UserService, __init__, greet, _internal +(3) |
4 exported |
code-intel/core/tests/parser-corpus/fixtures/ruby-sample.rb |
UserService, initialize, get_user, save_user +(3) |
7 exported |
code-intel/core/tests/parser-corpus/fixtures/typescript-sample.ts |
UserService, constructor, greet, createUser +(3) |
6 exported |
code-intel/core/tests/parser-corpus/fixtures/cpp-sample.cpp |
HttpServer, TcpServer, TcpServer, Config +(2) |
6 exported |
code-intel/core/tests/parser-corpus/fixtures/c-sample.c |
Point, server_init, server_start, internal_calc +(1) |
5 exported |
Entry Points
Start exploration here — exported symbols with no external callers:
server_init(function)→code-intel/core/tests/parser-corpus/fixtures/c-sample.c:17server_start(function)→code-intel/core/tests/parser-corpus/fixtures/c-sample.c:22internal_calc(function)→code-intel/core/tests/parser-corpus/fixtures/c-sample.c:27parse_config(function)→code-intel/core/tests/parser-corpus/fixtures/c-sample.c:32TcpServer(class)→code-intel/core/tests/parser-corpus/fixtures/cpp-sample.cpp:17TcpServer(function)→code-intel/core/tests/parser-corpus/fixtures/cpp-sample.cpp:19
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.
- yesterday First seen · 80 lines · 48 tokens per session scan A 30e1161d9d1f
fixtures is a skill published in the GitHub repository vohongtho/code-intel-platform (3 stars, last pushed 6d ago), licensed MIT. It adds 48 tokens to every session and 1,208 once invoked, about $0.0002 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-31.
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…