Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-skillsnpx agentmods add skills/bilal140202/the-lord-of-the-skills/codealive-ai__ai-driven-developmentWrote 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/skills/bilal140202/the-lord-of-the-skills/codealive-ai__ai-driven-development)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/codealive-ai__ai-driven-development"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/codealive-ai__ai-driven-development/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/skills/bilal140202/the-lord-of-the-skills/codealive-ai__ai-driven-development"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/codealive-ai__ai-driven-development.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.00084 | $0.01776 |
| Opus 5 | $0.00042 | $0.00888 |
| Sonnet 5 | $0.00017 | $0.00355 |
| Haiku 4.5 | $0.00008 | $0.00178 |
Grade A, and why
investigating-repository-history 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 8d 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.
This is a copy
100% identical to investigating-repository-history — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository History Investigator
Use this skill to reconstruct the historical intent behind code before changing it. The goal is not merely “find the blame commit”; the goal is to return a compact, cited history note explaining relevant PRs, review comments, constraints, rejected approaches, and anomalies.
Contents
- Trigger conditions
- Core rule
- Fast path
- Progressive disclosure
- Investigation workflow
- Evidence confidence rules
- Output template
- Gotchas
- Available scripts
Trigger conditions
Use this skill when the user asks any of these:
- “Why is this code written this way?”
- “Can I remove/simplify/change this check, constraint, branch, migration, public API, or feature flag?”
- “Which PR introduced this behavior or regression?”
- “Find the relevant PR/review discussion/history for this code.”
- Before editing code that touches API compatibility, security, concurrency, persistence, migrations, performance, generated interfaces, feature flags, or unclear legacy/workaround logic.
Do not use this skill for trivial new code with no dependency on existing behavior.
Core rule
Before making a risky edit, produce a history note answering:
- What code scope was inspected?
- Which commits and PRs are relevant?
- Which review comments or PR discussions explain intent?
- What constraints, risks, rejected approaches, or tests were found?
- Is the evidence strong, weak, contradictory, stale, truncated, or unknown?
- How should the implementation plan change?
If the evidence is weak, say UNKNOWN and lower confidence. Never invent intent from a semantic match alone.
Fast path
From the repository working tree, run the collector first. If the skill directory is not the current directory, prefix the script path with the installed skill path and pass --repo-dir /path/to/repo.
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.
- 8d ago First seen · 166 lines · 84 tokens per session scan A 8dd137259143
investigating-repository-history is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 84 tokens to every session and 1,776 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to investigating-repository-history, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ainb-fleet:ainb-spawn
Spawn a coding-agent session correctly with ainb run: always into a git worktree, never bare into a plain checkout. Use whenever you are about to start a Claude/Codex/Gemini/Copilot session in a terminal. Guards the invocations that silently produce a (broken) workspace row, two agents sharing one working tree, a…
serpsmith
Publish SEO articles reliably across AI-agent runtimes.
historian
Chesterton's Fence for code you're about to delete or refactor. Before you rip out a weird retry, a seemingly dead branch, an ugly workaround, or a "redundant" check whose purpose isn't obvious — find out why it exists first. git blame it, find the callers, read the linked issue/PR/commit. If you can't explain why the…
reverse-engineering-android-malware-with-jadx
Reverse engineers malicious Android APK files using JADX decompiler to analyze Java/Kotlin source code, identify malicious functionality including data theft, C2 communication, privilege escalation, and overlay attacks. Examines manifest permissions, receivers, services, and native libraries. Activates for requests…
hash-anchored-edit
A file-editing procedure that uses SHA-256 hashes to check whether a file changed before and after an edit. It also describes ownership rules for files handled by parallel agents.
building-threat-hunt-hypothesis-framework
Build a systematic threat hunt hypothesis framework that transforms threat intelligence, attack patterns, and environmental data into testable hunting hypotheses.