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 yunbow/ai-dev-os-plugin-claude-code --skill ai-dev-os-ticketgit clone --depth 1 https://github.com/yunbow/ai-dev-os-plugin-claude-codeWrote 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/yunbow/ai-dev-os-plugin-claude-code/ai-dev-os-ticket)<a href="https://agentmods.dev/skills/yunbow/ai-dev-os-plugin-claude-code/ai-dev-os-ticket"><img src="https://agentmods.dev/badge/skills/yunbow/ai-dev-os-plugin-claude-code/ai-dev-os-ticket/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/yunbow/ai-dev-os-plugin-claude-code/ai-dev-os-ticket"><img src="https://agentmods.dev/badge/skills/yunbow/ai-dev-os-plugin-claude-code/ai-dev-os-ticket.svg" alt="Reviewed on agentmods" width="80" 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.00066 | $0.01450 |
| Opus 5.5 | $0.00026 | $0.00580 |
| Sonnet 5.5 | $0.00013 | $0.00290 |
| Haiku 4.5 | $0.00007 | $0.00145 |
Grade A, and why
ai-dev-os-ticket 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 1mo 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Dev OS Ticket Generator
Execution Flow
1. Enter Plan Mode
Enter plan mode immediately. All analysis happens before any output is produced.
2. Analyze the Request
Parse the user's implementation request and identify:
- Goal: What needs to be built or changed
- Scope: New feature / bug fix / refactoring / enhancement
- Affected area: Which parts of the codebase are involved
3. Identify Affected Files
Search the codebase to determine:
- Files that will be modified
- Files that will be created
- Files that will be deleted
- Related files that provide context (imports, tests, configs)
4. Parse CLAUDE.md and Load Guidelines
Extract the list of guideline file paths from the project's CLAUDE.md. Read the referenced guideline files to understand the active rules.
5. Build Dynamic Mapping
Map affected files to their relevant guidelines using file pattern matching.
Examples by tech stack:
- Python:
*.py→ code.md, naming.md, validation.md;*/router.py→ security.md, cors.md;*/models.py→ naming.md, validation.md;*/schemas.py→ validation.md;alembic/**→ naming.md - Next.js:
*.tsx→ ui.md, form.md, code.md, naming.md;app/**/page.tsx→ routing.md;app/**/action.ts→ server-actions.md - Go:
*.go→ code.md, naming.md, error-handling.md
If checklist templates exist in the plugin's checklist-templates/ directory for the detected tech stack, load them as a reference.
6. Extract Relevant Checklist Items
From the mapped guidelines, extract items that are relevant to this specific change:
- Filter by keywords: "MUST", "MUST NOT", "PROHIBITED", "REQUIRED"
- If a guideline has
checklist: [...]in frontmatter, use those items - Discard items unrelated to the current scope (e.g., skip database rules if no DB changes)
7. Determine Ticket Output Destination
Look for a ## Ticket Settings section in the project's CLAUDE.md.
If found, parse the settings:
## Ticket Settings
- output: file # "file" or "github-issue"
- path: docs/tickets/phase1 # Required when output=file
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.
- 1mo ago First seen · 191 lines · 66 tokens per session scan A 3dcd869223a0
ai-dev-os-ticket is a skill published in the GitHub repository yunbow/ai-dev-os-plugin-claude-code (2 stars, last pushed 7mo ago), licensed MIT. It adds 66 tokens to every session and 1,450 once invoked, about $0.0003 per session on Opus 5.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
memstack-business-client-onboarding
Use this skill when the user says 'client onboarding', 'new client', 'onboard client', 'kickoff meeting', 'intake form', 'welcome email', or needs welcome sequences, questionnaires, and setup checklists for new clients. Do NOT use for contracts or invoicing.
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.
memstack-product-mvp-scoper
Use this skill when the user says 'MVP', 'minimum viable product', 'scope the MVP', 'what should I build first', 'strip to core', or needs to define the smallest build that validates a product hypothesis. Do NOT use for full PRDs or roadmap planning.
memstack-product-user-story-generator
Use this skill when the user says 'user stories', 'write stories', 'backlog', 'sprint planning', 'acceptance criteria', or needs prioritized stories with Given/When/Then criteria and story point estimates. Do NOT use for full PRDs or detailed feature specs.
memstack-marketing-marketplace-submit
Use when the user says 'submit to marketplace', 'publish my skill', 'share this skill', 'list on marketplace', 'submit plugin', 'publish to community', or needs to submit a skill or plugin to a community marketplace via PR. Do NOT use for building skills or writing plugin code.
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.