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/owainlewis/youtube-tutorialsWrote 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/commands/owainlewis/youtube-tutorials/history)<a href="https://agentmods.dev/commands/owainlewis/youtube-tutorials/history"><img src="https://agentmods.dev/badge/commands/owainlewis/youtube-tutorials/history/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/commands/owainlewis/youtube-tutorials/history"><img src="https://agentmods.dev/badge/commands/owainlewis/youtube-tutorials/history.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.00000 | $0.00250 |
| Opus 5.5 | $0.00000 | $0.00100 |
| Sonnet 5.5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
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 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.
What it actually says
History
Explore git history to understand what changed and why.
What to look for
$ARGUMENTS — e.g. "what changed in the last 3 commits", "who last changed this function", "what happened to auth.ts"
Tools
Recent commits
git log --oneline -N
Changes in a specific commit
git show <hash>
Who changed a specific file or line
git log --follow -p <file>
git blame <file>
Search commit messages
git log --grep="keyword"
Find when a line was introduced
git log -S "search string" --oneline
Instructions
- Understand what the user is looking for
- Use the appropriate git command to find it
- Summarize the findings in plain language — don't just dump raw output
- If looking at blame, explain the context of each change
Rules
- Translate git output into human-readable summaries
- When showing blame, include the commit message context — not just the hash
- For large histories, summarize the key changes rather than listing everything
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 · 49 lines · 0 tokens per session scan A 1ad864af71c9
history is a command published in the GitHub repository owainlewis/youtube-tutorials (408 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 250 tokens. 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 commands, from other repositories
changelog-auto
Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…
guardian
Revisión de código IA como pre-commit hook — Guardian Angel.
cm
Stage working tree changes and create a Conventional Commit (no push).
cp
Stage, commit, and push the current branch following git governance rules.
hotfix
An emergency software-fix workflow that moves directly from development to verification and Git commit, skipping the usual planning and design stages.
commit
A Git commit command that reviews changes, stages selected files, and creates a commit message following Conventional Commits, a shared format such as “fix: correct login error.”