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/recca0120/code-quest/parser-developmentnpx skills add recca0120/code-quest --skill parser-developmentgit clone --depth 1 https://github.com/recca0120/code-questWhat 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.00046 | $0.00929 |
| Opus 5 | $0.00023 | $0.00464 |
| Sonnet 5 | $0.00009 | $0.00186 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
parser-development 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parser Development
Architecture
CLI stdout (JSON line)
↓ ClaudeProtocol.parseLine() → ParseResult (ok | skip | unknown | error)
↓ ClaudeAdapter.transform() → AdapterOutput { events, autoResponses, controlResponses, serverActions }
↓ ProcessRunner._processLine() → emit('socket_event', SocketEvent)
↓ Socket.IO → Client
Key Types
| Type | File | Purpose |
|---|---|---|
ProtocolEvent |
apps/summoner/src/protocol/claude-schemas.ts |
Discriminated union of all CLI event types (21+) |
SocketEvent |
packages/shared/src/schemas/common.ts |
{ name: string; payload: Record<string, unknown> } |
ParseResult |
apps/summoner/src/protocol/provider-adapter.ts |
ok | skip | unknown | error discriminated union |
AdapterOutput |
apps/summoner/src/protocol/provider-adapter.ts |
events + autoResponses + controlResponses + serverActions |
Core Files
| File | Purpose |
|---|---|
apps/summoner/src/protocol/claude-schemas.ts |
Zod schemas for all event types, getSchemaForType(), KNOWN_EVENT_TYPES |
apps/summoner/src/protocol/claude.ts |
ClaudeProtocol.parseLine() — JSON parse → Zod validate → ParseResult |
apps/summoner/src/protocol/claude-adapter.ts |
ClaudeAdapter.transform() — dispatches on event.type → SocketEvent[] |
apps/summoner/src/protocol/provider-adapter.ts |
Abstract ProviderAdapter interface |
apps/summoner/src/protocol/server-action.ts |
ServerAction union: auto_respond, read_diff, forward_to_client |
apps/summoner/src/process-runner.ts |
Orchestrates parseLine → transform → emit |
parseLine Flow
parseLine(line: string): ParseResult {
// 1. Trim + JSON.parse (skip if empty or invalid)
// 2. Check type field exists (skip if missing)
// 3. Skip keep_alive events
// 4. Check KNOWN_EVENT_TYPES (return 'unknown' if not found)
// 5. getSchemaForType(type, subtype) → Zod safeParse
// 6. Return { status: 'ok', event } or { status: 'error', error: ZodError }
}
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 · 87 lines · 46 tokens per session scan A 214f936db022
parser-development is a skill published in the GitHub repository recca0120/code-quest (11 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 929 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…