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/avicorp/learning-dna-plugin/build-appnpx skills add avicorp/learning-dna-plugin --skill build-appgit 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/skills/avicorp/learning-dna-plugin/build-app)<a href="https://agentmods.dev/skills/avicorp/learning-dna-plugin/build-app"><img src="https://agentmods.dev/badge/skills/avicorp/learning-dna-plugin/build-app.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.04057 |
| Opus 5 | $0.00009 | $0.02028 |
| Sonnet 5 | $0.00003 | $0.00811 |
| Haiku 4.5 | $0.00002 | $0.00406 |
Grade A, and why
build-app 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build-app — Rebuild Learning App Data
Usage
/learning-dna:build-app — rebuild all topics
/learning-dna:build-app <topic> — rebuild a specific topic
Flow
Step 1: Scan Knowledge Directory
- Scan
knowledge/for topics with content (directories containingsources/with markdown files) - If a specific topic is provided, only process that topic
- Skip directories without source content
Step 2: Application Structure Setup
Only runs when
learning-app/does not exist. If the app already exists, skip to Step 3.
Set up the foundational project before any components are built:
- Initialize a React 19 + TypeScript + Vite 6 + Tailwind CSS 4 project in
learning-app/ - Add Mermaid 11 for diagram rendering and React Router for routing
- Create the full directory structure:
learning-app/ src/ components/ # Reusable components (TTSReader, Layout, Sidebar, Navbar, Footer) contexts/ # React Context providers hooks/ # Custom hooks (useTTS, useIndexedDB, useProgress) pages/ # Page components (Welcome, TopicHome, TopicDetail, Quiz, QuizStatus) data/ # Generated JSON data files types/ # TypeScript type definitions lib/ # Utility functions (IndexedDB loader) scripts/ # Parse scripts for knowledge → JSON - Create
src/types/index.tswith all TypeScript interfaces upfront (see Step 3 for the full type definitions) - Set up React Router with placeholder routes:
/— Welcome page/quiz-status— Quiz status page/:topic— Topic home page/:topic/:subtopic— Topic detail page/:topic/quiz— Quiz page
- Install all dependencies, configure Vite and Tailwind
Step 3: Data Model — React Context
Create a LearningContext in src/contexts/LearningContext.tsx that replaces all localStorage-based state management.
TypeScript Interfaces (in src/types/index.ts)
interface AppState {
topics: Topic[];
topicProgress: Record<string, TopicProgress>;
}
interface Topic {
slug: string;
name: string;
subtopics: string[];
}
interface TopicProgress {
learningStatus: boolean;
quizStatus: boolean;
lastScore: QuizScore | null;
subtopicStatus: Record<string, 'completed' | 'in-progress' | 'not-started'>;
lastVisited: string | null;
}
interface QuizScore {
total: number;
correct: number;
breakdown: {
easy: [number, number];
medium: [number, number];
hard: [number, number];
};
}
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 · 307 lines · 17 tokens per session scan A 2514c475f2b5
build-app is a skill 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 4,057 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
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
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 自测页.
grid-ctf-ops
Operational knowledge for the gridctf scenario including strategy playbook, lessons learned, and resource references. Use when generating, evaluating, coaching, or debugging gridctf strategies.