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/drafthq/draft/integrationsnpx skills add drafthq/draft --skill integrationsgit clone --depth 1 https://github.com/drafthq/draftWhat 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.00028 | $0.00410 |
| Opus 5 | $0.00014 | $0.00205 |
| Sonnet 5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
integrations 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.
What it actually says
Integrations Workflows
/draft:integrations is the canonical integrations parent command.
It handles connectors and exports to external systems like Jira.
Specialist integration workflows remain available as named modes:
/draft:jira preview(or/draft:integrations jira-preview)/draft:jira create(or/draft:integrations jira-create)
Step 1: Parse Intent and Route
Examine the user's input and route to the correct integrations workflow.
Explicit Named Modes
If the user explicitly invokes a specialist mode, route directly:
/draft:integrations jira-preview→ follow/draft:jira preview/draft:integrations jira-create→ follow/draft:jira create
Intent Routing
If no explicit mode is specified, infer the intent from the user's prompt:
| Intent | Action | Route |
|---|---|---|
| "Export to Jira", "Preview Jira issues", "Show me what you'll create in Jira" | Jira Preview | /draft:jira preview |
| "Create Jira issues", "Sync to Jira", "Make tickets" | Jira Create | /draft:jira create |
Step 2: Bare Parent Command Fallback
If the user runs a bare /draft:integrations without clear intent, present a small integrations menu with a recommended default path:
Draft Integrations Menu:
1. /draft:integrations jira-preview (Generate Jira export file for review)
2. /draft:integrations jira-create (Create Jira issues from export)
What integration action do you want to perform?
Do not automatically launch a specialist workflow without explicit or clear inferred intent.
Compatibility Note
The legacy specialist commands remain supported during the migration period, but /draft:integrations is the canonical parent for integration tasks.
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 · 54 lines · 28 tokens per session scan A 84815b261e5e
integrations is a skill published in the GitHub repository drafthq/draft (40 stars, last pushed 13d ago), licensed MIT. It adds 28 tokens to every session and 410 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-30.
Other skills, from other repositories
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.