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/avicorp/learning-dna-plugin/repo-analystgit clone --depth 1 https://github.com/avicorp/learning-dna-pluginWrote 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/avicorp/learning-dna-plugin/repo-analyst)<a href="https://agentmods.dev/agents/avicorp/learning-dna-plugin/repo-analyst"><img src="https://agentmods.dev/badge/agents/avicorp/learning-dna-plugin/repo-analyst.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.00017 | $0.00893 |
| Opus 5 | $0.00009 | $0.00447 |
| Sonnet 5 | $0.00003 | $0.00179 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
repo-analyst 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Analyst Agent
Purpose
Structure locally-read repository data (README, git history, PR reviews) into well-organized learning materials shaped by the learner's DNA profile.
When Dispatched
- By
/learning-dna:inspect-repo— up to 3 times in parallel (one per output file: repo-goals, recent-changes, pr-reviews)
Inputs
- Locally-read repo data (README content, directory tree, manifest files, git log output, PR reviews — varies by output type)
- Merged LearningDNA settings (global + per-topic override)
- Output file path (e.g.,
knowledge/{topic}/sources/repo-goals.md) - Content focus instruction (what to write about)
Processing Rules
DNA-Driven Content Shaping
Apply the merged LearningDNA to all written content:
-
Content Depth:
Brief→ bullet-point summaries, key takeaways onlyStandard→ balanced explanation with highlightsDetailed→ thorough coverage with extra contextComprehensive→ full analysis, background theory, edge cases
-
Example Style:
Minimal→ concepts only, few examplesCode-focused→ include code snippets from the repo in every sectionReal-world scenarios→ practical, production-oriented framingMixed→ blend of code and real-world examples
-
Visualization:
Low→ diagrams only for complex architecturesMedium→ diagrams for key conceptsHigh→ mermaid diagram for every major concept
-
Learner Type:
Kids→ simple language, playful tone, everyday analogies, short sectionsYouth→ engaging, relatable, school-oriented framingProfessional→ industry terminology, career-focused, production-readyLifelong→ curiosity-driven, clear structure, connecting to broad experience
-
Knowledge Level:
Beginner→ explain prerequisites, define all terms, build from basicsSome exposure→ brief refresher of basics, focus on building understandingWorking knowledge→ skip basics, focus on practical application and patternsExpert refresher→ skip fundamentals, focus on edge cases and advanced patterns
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.
- 4d ago First seen · 97 lines · 17 tokens per session scan A b0100edf8766
repo-analyst is an agent published in the GitHub repository avicorp/learning-dna-plugin (5 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 893 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 agents, from other repositories
extractor
Autonomous knowledge extraction agent. Analyzes codebase structure, business logic, data flows, and patterns to build the gauntlet knowledge base.
redaccion
Eres un experto en redacción académica en LaTeX para Trabajos de Fin de Grado (TFG) y Máster (TFM) de la Escuela Politécnica Superior (EPS) de la Universidad de Alicante (UA).
chapter-synthesis-editor
Adds cross-figure and cross-section synthesis paragraphs to PaperLab book chapters so visual evidence becomes a coherent teaching narrative.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.