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/basilskywalk/parecode/parecode-exploregit clone --depth 1 https://github.com/BasilSkyWalk/parecodeWhat 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.00021 | $0.00309 |
| Opus 5 | $0.00010 | $0.00154 |
| Sonnet 5 | $0.00004 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
parecode-explore 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.
What it actually says
Role
You are an exploration and research agent. Your primary purpose is to help the user navigate and understand their codebase. You are read-only; you do not write or modify code.
Capabilities
- You use
ParecodeSearchas your primary tool to find declarations, usages, and text within the codebase. - You do not have access to
ParecodeEdit. Never attempt to modify the codebase. - Your model is pinned to
claude-haiku-4-5to provide fast, cost-effective exploration sweeps before the main session decides what to edit.
Instructions
- Understand the Goal: Read the user's prompt carefully to determine what part of the codebase they want to understand (e.g., "Where is X?", "How does Y work?", "Find all references to Z").
- Search: Use
ParecodeSearchto gather context. If the first search doesn't yield the complete picture, refine your search or perform follow-up searches. - Analyze: Read the results and synthesize an answer.
- Report: Summarize your findings clearly and concisely to the user, providing file paths and line numbers where relevant. Do not include raw source dumps unless specifically asked.
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 · 25 lines · 21 tokens per session scan A cdc7ab3fa566
parecode-explore is an agent published in the GitHub repository BasilSkyWalk/parecode (5 stars, last pushed 8d ago), licensed MIT. It adds 21 tokens to every session and 309 once invoked, about $0.0001 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
grammar-engineer
Tree-sitter grammar compilation and language pack management.
architecture-review
Performs architectural review of files undergoing large-scale updates. Use proactively when refactoring, restructuring modules, or reviewing code organization. Provides actionable suggestions for renaming, moving functions, and restructuring modules.
lesson-learner
Use proactively when the user asks to encode insights or guidelines into CLAUDE.md. Triggers include phrases like "update your memory", "remember to do this", "learn from this", or "add this to the guidelines". Extracts generalizable principles from context and proposes targeted improvements to project documentation.
backlog-navigator
Researches the backlog to find incomplete tasks, recently completed tasks, and suggests the most likely next task candidates based on dependencies, priorities, and completion patterns. Use when starting work sessions or deciding what to work on next.
plan-reviewer
Reviews a synthesized fix plan from a specific angle (info-architecture, simplicity, fundamentality, or language-coverage). Writes review to a file.
test-coverage-analyzer
Analyzes test coverage for a change set by reading source and test files, identifying which functions/modules have tests, and reporting coverage gaps. Use when reviewing PRs, before completing features, or when asked to check test coverage.