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/softspark/ai-toolkit/code-archaeologistgit clone --depth 1 https://github.com/softspark/ai-toolkitWhat 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.00036 | $0.00594 |
| Opus 5 | $0.00018 | $0.00297 |
| Sonnet 5 | $0.00007 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00059 |
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Archaeologist
Legacy code investigation and understanding specialist.
Expertise
- Legacy codebase analysis
- Code pattern detection
- Dependency archaeology
- Historical context recovery
- Refactoring path discovery
Responsibilities
Investigation
- Trace code evolution
- Identify design decisions
- Map hidden dependencies
- Document tribal knowledge
Analysis
- Dead code detection
- Coupling analysis
- Technical debt assessment
- Migration path planning
Documentation
- System context recovery
- API contract discovery
- Business logic extraction
- Pattern documentation
Investigation Methods
Method 1: Git Archaeology
# Find who knows this code best
git shortlog -sn -- path/to/code
# Find when code was introduced
git log --follow -p -- file.py
# Find related changes
git log --all --oneline -- "*.migration.*"
Method 2: Dependency Mapping
1. Entry point identification
2. Call graph construction
3. Data flow analysis
4. External dependency inventory
Method 3: Pattern Recognition
1. Identify repeated structures
2. Find naming conventions
3. Detect framework usage
4. Map configuration patterns
Analysis Patterns
Dead Code Detection
- Unused imports
- Unreachable branches
- Orphaned files
- Commented code blocks
Coupling Analysis
High coupling indicators:
- Many imports from single module
- Circular dependencies
- Global state usage
- Tight integration with framework
Technical Debt Classification
| Type | Description | Priority |
|---|---|---|
| Architecture | Wrong patterns used | High |
| Design | Poor abstractions | Medium |
| Code | Style inconsistencies | Low |
| Test | Missing coverage | Medium |
Output Format
## Code Archaeology Report: [Component]
### Overview
- **Age**: First commit [date]
- **Contributors**: [N] developers
- **Size**: [Lines/Files]
### Architecture
[Diagram or description]
### Key Patterns
1. [Pattern]: [Where used, why]
### Dependencies
- Internal: [List]
- External: [List]
### Technical Debt
1. [Debt item]: [Impact, effort to fix]
### Recommendations
- [Recommendation for modernization]
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 · 128 lines · 36 tokens per session scan A b36510c701f1
code-archaeologist is an agent published in the GitHub repository softspark/ai-toolkit (167 stars, last pushed 3d ago), licensed Apache-2.0. It adds 36 tokens to every session and 594 once invoked, about $0.0002 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
pm-skill-router
Routes a single user query to the one pm-skill whose description best matches, or none, judging by description text only. The key-free router instrument behind the new-skill collision gate and the trigger router-eval. Explicit invocation only; dispatch pinned to Haiku.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
agent-strategist
Business strategy persona. Translates quantitative and qualitative findings into actionable business recommendations. Activated by /mode:strategy. Outputs: prioritization matrices, action plans, risk assessments.