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/destrayon/connapse/create-ticketsnpx skills add Destrayon/Connapse --skill create-ticketsgit clone --depth 1 https://github.com/Destrayon/ConnapseWrote 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/destrayon/connapse/create-tickets)<a href="https://agentmods.dev/skills/destrayon/connapse/create-tickets"><img src="https://agentmods.dev/badge/skills/destrayon/connapse/create-tickets.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.00062 | $0.01891 |
| Opus 5 | $0.00031 | $0.00945 |
| Sonnet 5 | $0.00012 | $0.00378 |
| Haiku 4.5 | $0.00006 | $0.00189 |
Grade A, and why
create-tickets 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Tickets
Turn a brainstorming conversation into well-structured, properly-sized GitHub issues.
Overview
After a discussion about features, improvements, or bugs, this skill:
- Extracts every idea from the conversation
- Decomposes large features into PR-sized sub-issues
- Presents a structured plan for user review
- Batch-creates all approved issues with proper metadata
- Adds them to the project board
Step 1: Extract Ideas from Conversation
Read the full conversation history. For each distinct idea, feature, bug, or task mentioned, capture:
- What it is (feature, bug fix, enhancement, refactor, docs, test, infrastructure)
- Why it matters (the user's stated motivation)
- Rough scope (how many files/areas it touches)
Group related ideas together. If the user discussed a large feature with multiple parts, keep those parts linked.
Step 2: Size and Decompose
Apply these sizing rules strictly:
| Size | Lines Changed | Files | Target |
|---|---|---|---|
| XS | < 50 | 1-2 | Ideal for config, typos, small fixes |
| S | 50-150 | 2-4 | Target size for most issues |
| M | 150-300 | 3-6 | Acceptable for focused features |
| L/XL | 300+ | 6+ | MUST be decomposed — never create as single issue |
For any idea estimated at L or larger, decompose by layer:
- Data layer: models, migrations, interfaces (S)
- Service layer: business logic implementing interfaces (S-M)
- Endpoint layer: API endpoints wired to service (S)
- UI layer: Blazor components consuming endpoints (S-M)
- Test layer: unit + integration tests (S-M)
Not every layer applies to every feature. Only create sub-issues for layers that are relevant.
Step 3: Structure Each Issue
For each issue, determine all metadata:
Title
- Concise, actionable, imperative voice
- Good: "Add multi-prefix OR-clause to cloud scope search"
- Bad: "Cloud scope search improvements"
Labels (one type, one or more area labels, and a size label)
Type labels (exactly one):
type: feature, type: bug, type: enhancement, type: refactor, type: docs, type: test, type: infrastructure
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.
- 4d ago First seen · 223 lines · 62 tokens per session scan A 17bda450fd01
create-tickets is a skill published in the GitHub repository Destrayon/Connapse (16 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 1,891 once invoked, about $0.0003 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
collattice
Operate a Collattice kanban board through its Model Context Protocol (MCP) endpoint — connecting, authentication, the board model, identifier rules (board-level reads need a board GUID, not a slug), the Markdown a board renders, and the full tool reference: reading and creating cards, moving and reordering lanes…
triage-tasks
Use when you want to review and batch-update open vault task statuses for the current project or across all projects.
tackle-task
Use when starting work on a specific vault task, when a task title or path is mentioned, or when coming from triage output.
add-task
Use when you want to quickly capture a new task in the vault from a title, with optional priority and due date.
owd-albatross
Connect, initialize, resume, or coordinate MDevolved Projects from Albatross using its agent.config.json stdio MCP surface, a pinned OAuth bridge, qualified tool names, workspace prompt continuity, path forks, resets, and independently attributable participant identities. Use when a repository runs Albatross, contains…
owd-eve
Connect, initialize, resume, or coordinate MDevolved Projects from an Eve agent using Eve's standard remote MCP connection, user-scoped Vercel Connect OAuth, qualified tool names, durable Project continuity, and independently attributable agent identities. Use when an Eve repository has agent/connections, when adding…