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 skills/alonf/mcppythondemo/branch-archaeologynpx skills add alonf/MCPPythonDemo --skill branch-archaeologygit clone --depth 1 https://github.com/alonf/MCPPythonDemoWrote 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/alonf/mcppythondemo/branch-archaeology)<a href="https://agentmods.dev/skills/alonf/mcppythondemo/branch-archaeology"><img src="https://agentmods.dev/badge/skills/alonf/mcppythondemo/branch-archaeology.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.00433 |
| Opus 5 | $0.00010 | $0.00217 |
| Sonnet 5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
branch-archaeology 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 3d 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
Context
Use this when a repository has milestone-named branches but branch names or tip commits are not trustworthy indicators of the actual teaching progression.
Patterns
- Start with the roadmap or lecture artifact (
docs/MCPDemoRoadmap.mdhere) to learn the intended milestones. - Verify each milestone by diffing the branch against the previous milestone and by reading the exact server/client files touched.
- Check branch containment (
git branch --contains <sha>) before assuming milestones are linear ancestors. - Prefer behavior over labels: summarize what tools, resources, prompts, transports, and safety mechanisms actually changed.
- Note documentation drift explicitly when README text lags behind the code.
Examples
- In
alonf/MCPDemo,milestone-1throughmilestone-7are best interpreted via roadmap plus file diffs; onlymilestone-7flows directly intomaster. masterdiffers frommilestone-7mostly by docs polish (docs/Milestone-*.gif) and minor solution metadata, so the runtime architecture is effectively the milestone-7 architecture.
Anti-Patterns
- Assuming milestone branches form a strict ancestry chain without checking.
- Using only branch tip commit messages to infer milestone content.
- Treating README prose as authoritative when branch code and roadmap disagree.
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.
- 3d ago First seen · 37 lines · 19 tokens per session scan A 6d0230358549
branch-archaeology is a skill published in the GitHub repository alonf/MCPPythonDemo (0 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 433 once invoked, about $0.0001 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-31.
Other skills, from other repositories
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
ljg-learn
Deep concept anatomist that deconstructs any concept through 8 exploration dimensions (history, dialectics, phenomenology, linguistics, formalization, existentialism, aesthetics, meta-philosophy) and compresses insights into an epiphany. Use when user asks to explain, dissect, or deeply understand a concept, term, or…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
pedagogy-review
Holistic pedagogical review of a lecture deck (.qmd or .tex). Checks narrative arc, prerequisite assumptions, worked examples, notation clarity, and deck-level pacing. Use when user says "pedagogy review", "does this teach well?", "is the flow right?", "will students follow?", "review the narrative", or before…