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/ashlrai/ashlr-plugin/ashlr-codex-parallel-explorenpx skills add ashlrai/ashlr-plugin --skill ashlr-codex-parallel-exploregit clone --depth 1 https://github.com/ashlrai/ashlr-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ashlrai/ashlr-plugin/ashlr-codex-parallel-explore)<a href="https://agentmods.dev/skills/ashlrai/ashlr-plugin/ashlr-codex-parallel-explore"><img src="https://agentmods.dev/badge/skills/ashlrai/ashlr-plugin/ashlr-codex-parallel-explore.svg" alt="Measured on agentmods" height="20"></a>What 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.00033 | $0.00151 |
| Opus 5 | $0.00016 | $0.00076 |
| Sonnet 5 | $0.00007 | $0.00030 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
ashlr-codex-parallel-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 3d 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
Ashlr Codex Parallel Explore
For multi-file work, split exploration into independent questions:
- One explorer maps ownership, entrypoints, and existing patterns.
- Another explorer audits risks, tests, and edge cases.
- Keep implementation local unless a worker can own a disjoint file set.
Use Ashlr tools in each exploration:
ashlr codex-start --json
Then prefer ashlr__orient, ashlr__grep, ashlr__tree, and ashlr__read before opening raw 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.
- 3d ago First seen · 21 lines · 33 tokens per session scan A 36bca99a78be
ashlr-codex-parallel-explore is a skill published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 151 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
rust-system-calls
Guides using bunsys for system calls and file I/O in Rust. Use when implementing file operations, opening fds, or any syscall path instead of std::fs or libc.
bunqueue-dev
Internal skill for contributing to bunqueue - architecture, testing, code conventions, and development workflow.
google-meet
Google Meet via gws: create spaces, fetch join links, list recordings.
people-crm
Turn LinkedIn connections (or any contact export) into a queryable personal CRM using the agent database.
clarify-spec
Full execution protocol for MODE: CLARIFY-SPEC -- resolving spec clarification markers and maintaining spec/planning alignment.
engineering-conventions
Codex adapter for opencode-swarm engineering invariants. Use before modifying plugin initialization, subprocesses, runtime portability, .swarm containment, plan durability, testrunner behavior, test-writing patterns, session/global state, guardrails/retry semantics, chat/system hooks, tool registration, release/cache…