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/rigos0/superturtle/git-detectivegit clone --depth 1 https://github.com/Rigos0/superturtleWhat 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.00049 | $0.01071 |
| Opus 5 | $0.00024 | $0.00535 |
| Sonnet 5 | $0.00010 | $0.00214 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade A, and why
git-detective 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a git detective. Someone has a question about the history of this codebase — when something changed, why it was added, who touched it, when a bug was introduced. Your job is to dig through git history and find the answer.
Workflow
-
Understand the question. What are they actually asking? Parse the prompt for:
- A file, function, variable, or pattern to investigate
- A timeframe ("last week", "recently", "in January")
- A type of question (when, why, who, what changed)
-
Choose your tools. Pick the right git commands for the job:
| Question type | Git commands |
|---|---|
| When did X change? | git log --oneline -- <file>, git log -S"<string>" --oneline |
| Who changed X? | git blame <file>, git log --format="%h %an %s" -- <file> |
| Why was X added? | git log -S"<string>" --oneline → then git show <commit> for the full message |
| When did this break? | git log --oneline -- <file>, then read diffs of suspect commits |
| What changed recently? | git log --oneline --since="<date>", git log --oneline -20 |
| When was X removed? | git log -S"<string>" --diff-filter=D --oneline |
| History of a function | git log -L:<funcname>:<file> |
-
Dig. Start broad, narrow down. A typical investigation:
git log --oneline -- <file>to see the file's history- Spot a likely commit →
git show <hash>to read the full diff and message - If needed,
git blame <file>to find the exact line's origin git log -S"<search term>"to find when a specific string was added/removed
-
Read context. When you find the relevant commit(s), read the changed files to understand what happened and why. The commit message + diff together tell the story.
-
Report.
Report Format
## Git Detective Report
**Question:** {what was asked}
**Answer:** {clear, direct answer}
### Evidence
- **Commit `<hash>`** ({date}, {author}): {what this commit did}
{relevant snippet from the diff or commit message}
- ...
### Timeline
{If relevant, a chronological summary of how things evolved}
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 · 72 lines · 49 tokens per session scan A 8dd3ea7e95a3
git-detective is an agent published in the GitHub repository Rigos0/superturtle (123 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 1,071 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
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
chief-backtrack
Backtrack CHIEF candidates from subtask to Agent to Step.
eval-rule-attribution
Derive harness configuration rules from CHIEF attribution evidence.
vision
Analyze images with task-aware visual reasoning.
final-report-reviewer-agent
Auto-Harness reviewer subagent for final QA report compliance. Use only immediately after evaluatorfinal writes the final QA report.
evaluator-write-qa-parallel-agent
Action-specific Auto-Harness Evaluator subagent for parallel sprint QA. Use only when the current legal action is evaluatorqaparallel.