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.
git clone --depth 1 https://github.com/jieapi/aicodeWrote 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/agents/jieapi/aicode/explore)<a href="https://agentmods.dev/agents/jieapi/aicode/explore"><img src="https://agentmods.dev/badge/agents/jieapi/aicode/explore/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/jieapi/aicode/explore"><img src="https://agentmods.dev/badge/agents/jieapi/aicode/explore.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00071 | $0.00655 |
| Opus 5.5 | $0.00028 | $0.00262 |
| Sonnet 5.5 | $0.00014 | $0.00131 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
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 1mo 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 1mo ago First seen · 32 lines · 71 tokens per session scan A 8dbc47d7f6c9
Explore is an agent published in the GitHub repository jieapi/aicode (87 stars, last pushed 1mo ago), licensed GPL-3.0. It adds 71 tokens to every session and 655 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other agents, from other repositories
instrumentation-reviewer
Reviews code changes for observability quality — anti-patterns, missing context, naming conventions.
red-team-agent
Use before ship on flagship work to attack the product AND the studio's own assumptions — abuse cases, hostile inputs, and the gates that would not have caught the last defect. Conditional role. Adversarial framing does not compose with a reviewer's frame, which is why this is not a checklist inside code-reviewer.
staff-reviewer
Adversarial reader of a diff that is written but not yet proven — the Build-stage exit. Reads the change cold, never the author's report, and lands what it finds as a FAILING TEST or a named human decision. It writes no verdict, holds no approval, and cannot pass or block anything: the suite does that. Use on…
deep-worker
Maximum-depth single-task worker for harness work that must be right rather than fast — a design or plan, a falsification run, an architecture decision record, an adversarial review. The default Opus at xhigh effort, always. Use when the orchestrator needs one isolated piece done thoroughly and will re-verify the…
system-architect
Use this agent for design-level judgment on a codebase, in two modes. MODE 1 — the SECOND half of the two-agent cross-validation code review workflow (paired with code-reviewer): evaluates a change's architecture soundness, design patterns, coupling/cohesion, scalability, data flow, API/contract design. MODE 2 …
code-reviewer
Use this agent to perform a thorough, line-level code review of recently written or changed code. This is the FIRST half of the two-agent cross-validation review workflow (paired with system-architect). It focuses on correctness, bugs, security (OWASP Top 10), style/convention adherence, and maintainability at the…