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/AnExiledDev/CodeForgeWrote 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/anexileddev/codeforge/git-archaeologist)<a href="https://agentmods.dev/agents/anexileddev/codeforge/git-archaeologist"><img src="https://agentmods.dev/badge/agents/anexileddev/codeforge/git-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/anexileddev/codeforge/git-archaeologist"><img src="https://agentmods.dev/badge/agents/anexileddev/codeforge/git-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.00136 | $0.03337 |
| Opus 5.5 | $0.00054 | $0.01335 |
| Sonnet 5.5 | $0.00027 | $0.00667 |
| Haiku 4.5 | $0.00014 | $0.00334 |
Grade A, and why
git-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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 274 lines · 136 tokens per session scan A 83f09bfa9d0b
git-archaeologist is an agent published in the GitHub repository AnExiledDev/CodeForge (10 stars, last pushed 2mo ago), with no licence file. It adds 136 tokens to every session and 3,337 once invoked, about $0.0005 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-31.
Other agents, from other repositories
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
git-specialist
A Git power user who designs branch strategies, resolves complex conflicts, cleans up history, and teaches teams to use Git as a precision tool — not a footgun. Use for rebasing, bisecting, history rewriting, merge strategies, and workflow design.
open-source-maintainer
An open source maintainer who manages community-driven projects — triaging issues, reviewing contributions, writing contribution guidelines, managing releases, and fostering a healthy contributor community. Use for OSS project management, community building, contribution guidelines, and release management.
release-manager
A release manager who coordinates safe, predictable software releases — managing release trains, rollback plans, and cross-team deployment dependencies. Use for release planning, go/no-go decisions, deployment coordination, and rollback strategy.
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.