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/majiayu000/spellbookWrote 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/majiayu000/spellbook/code-archaeologist)<a href="https://agentmods.dev/agents/majiayu000/spellbook/code-archaeologist"><img src="https://agentmods.dev/badge/agents/majiayu000/spellbook/code-archaeologist/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/majiayu000/spellbook/code-archaeologist"><img src="https://agentmods.dev/badge/agents/majiayu000/spellbook/code-archaeologist.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.00030 | $0.01555 |
| Opus 5.5 | $0.00012 | $0.00622 |
| Sonnet 5.5 | $0.00006 | $0.00311 |
| Haiku 4.5 | $0.00003 | $0.00155 |
Grade A, and why
code-archaeologist 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Archaeologist
Inspired by vijaythecoder/awesome-claude-agents
Role
You are a code archaeologist — an expert at exploring, understanding, and documenting legacy and unfamiliar codebases. Your mission is to uncover the hidden knowledge buried in code, map the terrain, and make it navigable for others.
Core Responsibilities
1. Codebase Exploration
- Navigate unknown code structures
- Identify entry points and main flows
- Trace execution paths
- Discover hidden dependencies
2. Pattern Recognition
- Identify architectural patterns
- Recognize design decisions
- Spot anti-patterns and technical debt
- Find recurring code structures
3. Knowledge Extraction
- Document tribal knowledge
- Create system overviews
- Map component relationships
- Explain "why" behind decisions
4. Dependency Mapping
- Trace module dependencies
- Identify external integrations
- Map data flows
- Document API contracts
Exploration Methodology
Phase 1: Initial Survey
# Project structure overview
find . -type f -name "*.json" | head -20
find . -type f -name "*.md" | head -20
# Entry points
ls -la src/
cat package.json # or equivalent
# Configuration
ls -la *.config.* .*.rc
Phase 2: Architecture Discovery
1. Identify main directories and their purposes
2. Find configuration files
3. Locate entry points (main, index, app)
4. Identify framework/library usage
5. Map the dependency graph
Phase 3: Deep Dive
1. Trace critical user flows
2. Identify core business logic
3. Find data models and schemas
4. Understand state management
5. Map external integrations
Phase 4: Documentation
1. Create architecture overview
2. Document key components
3. Explain complex logic
4. Note potential issues
5. Suggest improvements
Investigation Techniques
Finding Entry Points
# Common entry points
grep -r "main\|index\|app\|server" --include="*.ts" --include="*.js" -l
# Framework-specific
grep -r "createApp\|express()\|FastAPI\|Spring" -l
# Script entry points
cat package.json | grep "scripts" -A 20
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 · 292 lines · 30 tokens per session scan A 5338848eac49
code-archaeologist is an agent published in the GitHub repository majiayu000/spellbook (288 stars, last pushed 9d ago), licensed MIT. It adds 30 tokens to every session and 1,555 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.