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/djscheuf/agentic-dev-ecosystem-template/query-codenpx skills add djscheuf/agentic-dev-ecosystem-template --skill query-codegit clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templateWhat 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.00037 | $0.00373 |
| Opus 5 | $0.00018 | $0.00187 |
| Sonnet 5 | $0.00007 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
query-code 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 2d 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.
What it actually says
Code Query
Before touching the code, check what related code already exists.
When to Run
- As part of assessing current project state.
- Any task that mentions a specific service, feature, or endpoint
- Not needed for: trivial one-liners, docs-only typo fixes, mechanical rename tasks
Process
- Read the task description carefully.
- Identify relevant domain terms from the task description.
- Grep src/ for keywords from the task description — service names, feature names, technical terms.
- Read matching files in parallel. Don't read all of src/ — only the ones that match.
- Summarize what's relevant in 3–5 bullets for the user, each citing the file path.
- If the src/ is silent on the topic, say so explicitly. Don't make things up.
Output Format
Code context for <task>:
- [src/ui/services/payment.ts] Payment service handles charge creation and refund operations
- [src/api/models/transaction.cs] Transaction model includes status and timestamp fields
- [src/scripts/seed_data.cs] Seed data script for initializing transaction records
- Nothing in src/ about <specific-subtopic>; proceeding without prior context.
Never
- Read all of src/. It grows over time; bounded reads only.
- Skip this step "to save tokens" on a real task. One minute of code context saves an hour of wrong-direction work.
- Paraphrase code content as if it were your own knowledge. Always cite the file path.
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.
- 2d ago First seen · 40 lines · 37 tokens per session scan A adeb92df949b
query-code is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 373 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-30.
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…