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/sananthanarayan/skilldrop/guide-buildernpx skills add sananthanarayan/skilldrop --skill guide-buildergit clone --depth 1 https://github.com/sananthanarayan/skilldropWhat 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.00102 | $0.01680 |
| Opus 5 | $0.00051 | $0.00840 |
| Sonnet 5 | $0.00020 | $0.00336 |
| Haiku 4.5 | $0.00010 | $0.00168 |
Grade A, and why
guide-builder 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 2d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
guide-builder
You help the user turn rough material — notes, a spec, an architecture description, an endpoint list — into a guide a reader can follow top-to-bottom without you in the room. This skill picks one of three styles from the content; it is not the SRE operational runbook (runbook-generator) and not a design proposal for review (design-doc). It explains and instructs; it does not propose or page.
How to respond
-
Detect the style first, and say which you picked. Classify the input into exactly one of three styles using the table below. State the choice in one line with a one-clause why — "Reading this as a setup guide (it's install + config steps); say the word if you wanted the design walkthrough." — so the user can redirect before you draft.
Style Pick when the content is… Signals in the input Setup guide → templates/setup-guide.mdinstall / configure / run something, step by step "install", "set up", "getting started", prerequisites, env vars, .env, CLI commands,docker, "clone the repo"Design walkthrough → templates/design-walkthrough.mdexplaining how an already-decided system works so someone can understand or build on it components, data flow, "how X works", onboarding a new engineer, "why it's built this way" API reference → templates/api-reference.mdcontracts other developers code against endpoints, request/response shapes, OpenAPI, event names, payload schemas, status codes, webhooks, Kafka/SNS topics, JSON Schema -
Handle mixed content by picking the dominant style, not blending. If the input spans two styles (e.g. setup steps and the API they expose), lead with the dominant one and append the secondary as a clearly-labelled section or link out to a second guide. Only ask the user which to lead with if it's a genuine 50/50.
-
Gather only what the chosen style can't do without. Don't run a generic intake. Cap at 2 questions, pick defaults for the rest:
- Setup guide needs the target end state ("running locally" vs "deployed to staging") and the prerequisites baseline. Without an end state, a setup guide has no finish line.
- Design walkthrough needs who it's for (new hire vs adjacent team) and what they should be able to do after reading.
- API reference needs the transport + auth model and versioning scheme. Without auth, the examples are unrunnable.
What ships with it
5 files 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.
- 2d ago First seen · 77 lines · 102 tokens per session scan A cb2ea08b8868
guide-builder is a skill published in the GitHub repository sananthanarayan/skilldrop (2 stars, last pushed 18d ago), licensed MIT. It adds 102 tokens to every session and 1,680 once invoked, about $0.0005 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
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
openlore-analyze-codebase
Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.
openlore-review-changes
Review code changes using OpenLore risk, call, coverage, and cluster evidence without editing code. Use when asked for a change review, pre-PR safety check, or merge recommendation.
architect-implement
Generate a full Architecture Description (AD.md) from accepted ADRs using multi-agent DAG orchestration. Use when accepted ADRs exist and you need to produce or update unified architecture documentation.
team-repair
Re-index OKF v0.2 index.md/log.md files, derive CDR.md, rebuild .skills.json and AGENTS.md in team-ai-directives, migrate v0.1→v0.2 frontmatter, scan for rule conflicts, and verify directive freshness. Use when indexes are inconsistent, orphans are detected, after bulk changes, or for periodic team AI directives…
mission-brief
Mission-driven SDD orchestrator: take a feature description, structure it into a Mission Brief (goal, constraints, success criteria), generate an ordered step list with prompts that trigger installed SDD skills via model invocation or command-file discovery, and walk those steps to converged implementation. Use when…