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 skills add OutlineDriven/outline-driven-development --skill automatic-freeform-graphs-designgit clone --depth 1 https://github.com/OutlineDriven/outline-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/outlinedriven/outline-driven-development/automatic-freeform-graphs-design)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/automatic-freeform-graphs-design"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/automatic-freeform-graphs-design.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.00877 |
| Opus 5 | $0.00017 | $0.00439 |
| Sonnet 5 | $0.00007 | $0.00175 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
automatic-freeform-graphs-design 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- automatic-freeform-graphs-design — 100% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automatic freeform graphs design
Contract
| Field | Bound contract |
|---|---|
| Trigger | User wants a looser conceptual graph for exploratory work. |
| Authority | Reversible local: writes only one named freeform conceptual graph artifact to the working directory; rollback is deleting or overwriting that file. No remote mutation. |
| Side effect | A freeform conceptual graph artifact for exploration, written to the local filesystem. |
| Done | A freeform conceptual graph is generated and can be used for exploration. |
Inputs
- Exploratory topic or problem statement (required): the subject area to map. May be a question, a half-formed idea, a domain, or a set of related concerns.
- Existing notes or fragments (optional): prior concepts, questions, or connections the graph should incorporate.
- Output path (optional): where to write the graph artifact. Defaults to a file in the working directory.
Procedure
- Read the exploratory topic and any supplied notes. Identify the kind of exploration: open-ended question, design-space survey, concept mapping, or unknown-territory scouting. Done when: the exploration type is identified from the topic and notes.
- Extract concepts, questions, unknowns, and hypotheses as candidate nodes. Do not force them into a dependency order: this is exploration, not execution planning. Done when: candidate nodes are extracted without imposing a dependency order.
- Map relationships between nodes as labeled edges. Use relationship types suited to exploration: influences, tensions, supports, contradicts, depends-on-maybe, raises-question-of, and unknown-link. Allow cycles, bidirectional edges, and self-references where the exploration calls for them. Done when: edges are mapped with exploration-suited relationship labels, allowing cycles.
- Mark each node and edge with a confidence marker: certain, suspected, or unknown. Mark open questions explicitly so the graph surfaces what is not yet known. Done when: every node and edge has a confidence marker and open questions are marked.
- Identify clusters of tightly connected nodes and label them as provisional themes. Identify bridges between clusters as high-value exploration targets. Done when: clusters are labeled as themes and bridges are identified as high-value targets.
- Write the graph as a text artifact: a node list with confidence markers, an edge list with relationship labels, a cluster summary, the high-value bridge targets identified in step 5, and a list of open questions. Use a plain-text or markdown format that a human can read and revise without tooling. Done when: the graph artifact is written with all five sections in human-readable format.
- Review the graph against the original topic. Check that it surfaces the key unknowns without imposing a false dependency order. If a region is sparse or missing, add nodes and edges rather than leaving gaps. Done when: the graph surfaces key unknowns and has no false dependency order or sparse gaps.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · -12 tokens per session 7cb9224ecfd1
- 3d ago First seen · 42 lines · 47 tokens per session scan A 14975beed2ee
automatic-freeform-graphs-design is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 2d ago), licensed Apache-2.0. It adds 35 tokens to every session and 877 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
book-to-skill
Use when the user names one book, course, paper, or source document and asks to distill it into a reusable skill. Classifies the source as procedure or reference, writes an attributed SKILL.md, and proves its routing. Not for a folder of sources — use map-corpus.
drill
Use when a concept needs practising rather than explaining: run a scaffolded exercise from worked example to independent problem, quiz the learner, run spaced recall over what they cleared, or probe for the gaps blocking what they want next. For explanation, use explain-concept; for an end-to-end build, use capstone.
writing-lean-proofs
Use when asked to design, write, review, refactor, lint, or performance-diagnose Lean 4 proofs, libraries, or tactics. Not for non-Lean code or changes outside source, API, proof, or linter scope.
scaffold-exercises
Use when a course needs numbered problem, solution, and explainer scaffolds. Creates type-specific files with non-colliding names, populates them, and validates with the course linter. Not for a CLI or Next.js project scaffold — use scaffold-cli or scaffold-nextjs.
explain-concept
Use when a concept needs making clear rather than practising: build the intuition, explain why it exists and what it replaced, trace where it came from, draw it, or contrast it against what it gets confused with. For exercises and grading, use drill.
capstone
Use when the user is ready to apply what they learned to something real: scope a project sized to what they have cleared, write the brief with milestones and a done test, then judge the finished work against it. For single-concept exercises and quizzes, use drill.