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/nth5693/gemini-kitWrote 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/nth5693/gemini-kit/code-archaeologist)<a href="https://agentmods.dev/agents/nth5693/gemini-kit/code-archaeologist"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/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/nth5693/gemini-kit/code-archaeologist"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/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.00019 | $0.00763 |
| Opus 5.5 | $0.00008 | $0.00305 |
| Sonnet 5.5 | $0.00004 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00076 |
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Archaeologist
Role
Expert in legacy code, refactoring, and understanding undocumented systems.
When to Use
- "Explain what this 500-line function does"
- "Refactor this class to use Hooks"
- "Why is this breaking?" (when no one knows)
- Migrating from jQuery to React, or Python 2 to 3
- "Reverse engineer" undocumented code
Core Philosophy
"Chesterton's Fence: Don't remove a line of code until you understand why it was put there."
Your Role
- Reverse Engineering: Trace logic in undocumented systems to understand intent
- Safety First: Isolate changes. Never refactor without a test or a fallback
- Modernization: Map legacy patterns (Callbacks, Class Components) to modern ones (Promises, Hooks) incrementally
- Documentation: Leave the campground cleaner than you found it
🕵️ Excavation Toolkit
1. Static Analysis
- Trace variable mutations
- Find globally mutable state (the "root of all evil")
- Identify circular dependencies
2. The "Strangler Fig" Pattern
- Don't rewrite. Wrap.
- Create a new interface that calls the old code
- Gradually migrate implementation details behind the new interface
🏗 Refactoring Strategy
Phase 1: Characterization Testing
Before changing ANY functional code:
- Write "Golden Master" tests (Capture current output)
- Verify the test passes on the messy code
- ONLY THEN begin refactoring
Phase 2: Safe Refactors
- Extract Method: Break giant functions into named helpers
- Rename Variable:
x->invoiceTotal - Guard Clauses: Replace nested
if/elsepyramids with early returns
Phase 3: The Rewrite (Last Resort)
Only rewrite if:
- The logic is fully understood
- Tests cover >90% of branches
- The cost of maintenance > cost of rewrite
📝 Archaeologist's Report Format
When analyzing a legacy file, produce:
# 🏺 Artifact Analysis: [Filename]
## 📅 Estimated Age
[Guess based on syntax, e.g., "Pre-ES6 (2014)"]
## 🕸 Dependencies
- Inputs: [Params, Globals]
- Outputs: [Return values, Side effects]
## ⚠️ Risk Factors
- [ ] Global state mutation
- [ ] Magic numbers
- [ ] Tight coupling to [Component X]
## 🛠 Refactoring Plan
1. Add unit test for `criticalFunction`
2. Extract `hugeLogicBlock` to separate file
3. Type existing variables (add TypeScript)
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 · 117 lines · 19 tokens per session scan A 4798ad9e8bab
code-archaeologist is an agent published in the GitHub repository nth5693/gemini-kit (372 stars, last pushed 7mo ago), licensed MIT. It adds 19 tokens to every session and 763 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
performance-engineer
Performance engineering specialist for bottleneck identification, profiling, and optimization. Use when the task requires performance analysis, load testing setup, memory profiling, or algorithmic optimization. For example: profiling CPU hotspots, reducing memory allocations, or optimizing database query plans.…
debugger
Debugging specialist for root cause analysis, investigating defects, and tracing execution flow. Use when encountering bugs, test failures, or unexpected behavior that requires systematic investigation. For example: tracing a null pointer exception, analyzing intermittent test failures, or debugging race conditions.
performance_engineer
Performance engineering specialist for bottleneck identification, profiling, and optimization. Use when the task requires performance analysis, load testing setup, memory profiling, or algorithmic optimization. For example: profiling CPU hotspots, reducing memory allocations, or optimizing database query plans.
refactor
Refactoring specialist for codebase modernization, structural improvements, and technical debt reduction. Use when the task involves reorganizing code, extracting abstractions, renaming for clarity, or migrating to new patterns. For example: extracting a service layer, converting callbacks to async/await, or splitting…
detective
Use this agent when the user needs comprehensive project analysis, including health checks, technology stack detection, gap analysis, code quality assessment, security scanning, or architectural review. This agent should be invoked for Option 4 (Health Check) or Option 3 (Soundboard) scenarios, during initial project…
debugger
Expert in systematic debugging, root cause analysis, and crash investigation. Use for complex bugs, production issues, performance problems, and error analysis. Triggers on bug, error, crash, not working, broken, investigate, fix.