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 agents/nth5693/gemini-kit/code-archaeologistgit clone --depth 1 https://github.com/nth5693/gemini-kitWhat 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.00019 | $0.00763 |
| Opus 5 | $0.00010 | $0.00381 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 117 lines · 19 tokens per session scan A 4798ad9e8bab
code-archaeologist is an agent published in the GitHub repository nth5693/gemini-kit (374 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 763 once invoked, about $0.0001 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-30.
Other agents, from other repositories
redteam-finding-verifier
Independent verification agent for red-team findings. Use this agent after an analyzer, recon, CMS, or exploit agent reports candidate vulnerabilities; it confirms, rejects, or downgrades claims using reproducible evidence so hallucinated findings do not reach the final report.
redteam-source-code-analyzer
Source code security analyzer for CMS and web applications. Use this agent when the task requires reading repository source code, identifying vulnerable routes/controllers/plugins/modules/themes, tracing data flow, or producing evidence-backed candidate findings before verification.
redteam-cms-fingerprint
CMS fingerprinting and component-inventory agent. Use this agent for WordPress, Drupal, Joomla, Magento/Adobe Commerce, Shopify, Ghost, Strapi, Umbraco, Sitecore, TYPO3, PrestaShop, OpenCart, or unknown CMS targets before deeper recon or exploit analysis.
redteam-report-writer
Final report writer for red-team workflows. Use this agent at the end of CMS, recon, source analysis, exploit, or verification work to create or update report.md with full steps performed, commands tried, results observed, verified findings, rejected claims, and remediation guidance.
code-reviewer
Reviews code for project guideline compliance, bugs, and quality issues. Use after writing code, before commits, or before PRs. Specify files to review or defaults to unstaged git changes. High-confidence issues only (80+) to minimize noise.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…