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 Dragoon0x/dragoon-skills --skill installgit clone --depth 1 https://github.com/Dragoon0x/dragoon-skillsWrote 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/dragoon0x/dragoon-skills/install)<a href="https://agentmods.dev/skills/dragoon0x/dragoon-skills/install"><img src="https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/install.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.1 | $0.00083 | $0.00506 |
| Opus 5 | $0.00042 | $0.00253 |
| Sonnet 5 | $0.00017 | $0.00101 |
| Haiku 4.5 | $0.00008 | $0.00051 |
Grade A, and why
install 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 8d 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
/install
Sets up dragoon across every supported coding agent on the machine.
When to use
- The user is installing dragoon for the first time
- The user wants to add dragoon to a new agent
- The user mentions "setup", "install", "configure dragoon"
- The user wants to uninstall dragoon
Run it
# default install (auto-detects all hosts)
./setup
# specific hosts
./setup --hosts claude-code,cursor
# dry run (see what would happen)
./setup --dry-run
# uninstall
./setup --uninstall
# list supported hosts
./setup --list-hosts
What it does
- Copies the dragoon source pack to
~/.dragoon/ - For each detected host, symlinks (or copies if symlinks unsupported)
~/.dragooninto the host's skills directory:- claude-code:
~/.claude/skills/dragoon - codex:
~/.codex/skills/dragoon - cursor:
~/.cursor/skills/dragoon - opencode:
~/.opencode/skills/dragoon - factory:
~/.factory/skills/dragoon - kiro:
~/.kiro/skills/dragoon
- claude-code:
- Verifies the dragoon binary works
Requirements
- node 18 or higher
- bash 4 or higher
- one or more supported coding agents installed
That's it. Zero npm dependencies. No registry account needed.
Updating
Re-run ./setup from the latest source. The script does an idempotent rsync.
Uninstall
./setup --uninstall
Removes the dragoon symlink/copy from every host that has it. Leaves ~/.dragoon/ source untouched (delete it manually if desired).
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.
- 8d ago First seen · 68 lines · 83 tokens per session scan A c5940a0fd8bc
install is a skill published in the GitHub repository Dragoon0x/dragoon-skills (4 stars, last pushed 4mo ago), licensed MIT. It adds 83 tokens to every session and 506 once invoked, about $0.0004 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
design-system-tokens
Design token management with the W3C Design Token spec, three-tier hierarchy (global/alias/component), OKLCH color, Style Dictionary transforms, and dark mode theming. Use when creating token files, implementing theme systems, or building design-to-code pipelines.
Dark Mode Bug Finder
Detect dark mode rendering issues including contrast failures, missing theme tokens, image inversions, and transition glitches across components.
figma-extract-design-system
Extract a design system from vibe-coded production apps that never had one: inventory components, mine de-facto styling into DTCG tokens, scaffold a Storybook package, port components, and optionally round-trip tokens/components into Figma. Use when the user wants to 'extract a design system', 'create a design system…
figma-blame-node
Find which Figma version introduced a specific change — a component property or a child node — via a binary search over version history (log2(N) API calls instead of N). Answers 'who added this and when'. Use when the user wants git-blame-style attribution for a Figma design — triggers: 'when was this component…
figma-export-tokens
Export Figma variables to design token files in DTCG, CSS custom properties, Tailwind v4/v3, SCSS, TypeScript, JSON, Style Dictionary, or Tokens Studio. Use when the user wants to pull design tokens OUT of Figma into code — triggers: 'export tokens', 'export Figma variables', 'generate CSS variables from Figma', 'turn…
figma-generate-component-doc
Generate complete Markdown documentation for a Figma component — anatomy/layer tree, design tokens (colors, spacing, typography), states/variants matrix, accessibility notes, content guidelines, and optional code-parity + YAML frontmatter. Use when the user wants a docs page or handoff spec for a component or…