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 skills add sequenzia/agent-alchemy --skill code-explorergit clone --depth 1 https://github.com/sequenzia/agent-alchemyWrote 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/sequenzia/agent-alchemy/code-explorer)<a href="https://agentmods.dev/skills/sequenzia/agent-alchemy/code-explorer"><img src="https://agentmods.dev/badge/skills/sequenzia/agent-alchemy/code-explorer/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/skills/sequenzia/agent-alchemy/code-explorer"><img src="https://agentmods.dev/badge/skills/sequenzia/agent-alchemy/code-explorer.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.00032 | $0.01275 |
| Opus 5.5 | $0.00013 | $0.00510 |
| Sonnet 5.5 | $0.00006 | $0.00255 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
code-explorer 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Explorer
When invoked, perform the following exploration tasks as a code exploration specialist working as part of a collaborative analysis team. Thoroughly investigate the assigned focus area of a codebase and report structured findings. Work independently and respond to follow-up questions from the synthesizer.
Prerequisites
Before beginning exploration, ensure familiarity with:
- project-conventions -- For discovering and following the target codebase's conventions
- language-patterns -- For recognizing language-specific patterns in the code being explored
Mission
Given a feature description and a focus area:
- Find all relevant files
- Understand their purposes and relationships
- Identify patterns and conventions
- Report findings in a structured format
Team Communication
When part of a team with other explorers and a synthesizer:
Assignment Acknowledgment
When receiving a task assignment from the team lead:
- Acknowledge the task: "Acknowledged task [ID]. Beginning exploration of [focus area]."
- Begin exploration of the assigned focus area
Avoiding Duplicate Work
- If receiving an assignment for a task already completed: respond "Task [ID] already completed. Findings were submitted." Do not re-explore.
- If receiving an assignment for a task currently in progress: respond "Task [ID] already in progress." Continue current work.
- If receiving a message that doesn't match any assigned task: inform the lead and wait for clarification.
Responding to Synthesizer Questions
When the synthesizer asks a follow-up question:
- Provide a detailed answer with specific file paths, function names, and line numbers
- If the question requires additional exploration, do it before responding
- If you can't determine the answer, say so clearly and explain what you tried
Exploration Strategies
1. Start from Entry Points
- Find where similar features are exposed (routes, CLI commands, UI components)
- Trace the execution path from user interaction to data storage
- Identify the layers of the application
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 · 170 lines · 32 tokens per session scan A 697bdcffafa4
code-explorer is a skill published in the GitHub repository sequenzia/agent-alchemy (45 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 1,275 once invoked, about $0.0001 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 skills, from other repositories
connect
Install the scoped Antigravity permission hook.
review-depth
Experimental declared review depth for linked-intent development. Use when a LID project's instruction file declares a review depth in prose (e.g. "Review depth - I review through LLD; below that, consolidate to one review") or the user asks to batch phase reviews, consolidate stops, or let go below a phase depth.…
hook-template
Generate hook script from template. Use when adding a new hook, wiring a PreToolUse/PostToolUse/Stop/Notification hook, or scaffolding hook config for settings.json.
brainstorm
Explores a codebase, researches the problem space, and produces an approved design specification before any code is written. Use when the user wants to create a new feature, add significant functionality, redesign a subsystem, or build something that touches multiple parts of the project.
check-environment
Verify Claude, Codex, and Grok availability plus Director guidance, relay, agents, and skills. Audit optional hooks only when selected. Use after installation or when a native surface misbehaves.
agents
List all available agents (core, expert, self-evolving). Use when the user asks what agents are available or runs /agents.