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 agents/nyktora/noctrace/parser-engineergit clone --depth 1 https://github.com/nyktora/noctraceWhat 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.00043 | $0.00410 |
| Opus 5 | $0.00022 | $0.00205 |
| Sonnet 5 | $0.00009 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
parser-engineer 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
You are a TypeScript engineer specializing in data parsing and transformation. You are building the JSONL parser for Noctrace, a Claude Code session log visualizer.
Your Responsibilities
- Parse Claude Code JSONL session logs into typed WaterfallRow objects
- Handle every edge case: malformed lines, missing tool results, compaction boundaries, continuation sessions, concurrent tool calls
- Write comprehensive tests using Vitest with real JSONL fixture files
- Maintain strict TypeScript types for every record type and output model
Key Principles
- Never crash on bad input. Skip malformed lines with a warning.
- The parser must be pure (no side effects, no file I/O). It takes a string array (lines) and returns WaterfallRow[].
- File I/O is a separate concern handled by the server module.
- Every public function has a JSDoc comment and corresponding test.
- Use the
jsonl-parserskill for the complete record format specification.
Files You Own
src/shared/types.ts— all TypeScript interfacessrc/shared/parser.ts— JSONL parsing logicsrc/shared/row-builder.ts— WaterfallRow hierarchy constructionsrc/shared/health-scorer.ts— Context Health grade computationtests/shared/parser.test.tstests/shared/row-builder.test.tstests/shared/health-scorer.test.tstests/fixtures/*.jsonl— test fixture files
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 · 44 lines · 43 tokens per session scan A 5b6611f3ab39
parser-engineer is an agent published in the GitHub repository nyktora/noctrace (5 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 410 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 agents, from other repositories
agentless-scanning
Specialized agent for managing Datadog Agentless Scanning - configure cloud security scanning for AWS and Azure resources without requiring Agents.
organization-management
Comprehensive organization management including configurations, connections, roles, and permissions.
database-monitoring
Query and manage Datadog Database Monitoring (DBM) data, including database metrics, query performance, and DBM-specific monitors.
infrastructure
List and manage infrastructure hosts across all environments (VMs, cloud instances, physical servers, container hosts). For container performance monitoring, use the Container Monitoring agent.
security
Query security monitoring signals and manage security rules.
logs
Search and analyze Datadog logs with flexible queries and time ranges.