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/yugasun/aiops/to-issuesnpx skills add yugasun/aiops --skill to-issuesgit clone --depth 1 https://github.com/yugasun/aiopsWrote 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/yugasun/aiops/to-issues)<a href="https://agentmods.dev/skills/yugasun/aiops/to-issues"><img src="https://agentmods.dev/badge/skills/yugasun/aiops/to-issues.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.00021 | $0.00771 |
| Opus 5 | $0.00010 | $0.00385 |
| Sonnet 5 | $0.00004 | $0.00154 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
to-issues 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 5d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Break work into tracer-bullet vertical slices — each cuts all layers end-to-end, demoable alone.
Run /aiops-setup if tracker config is missing.
Modes
- Multi-session (PRD exists): full issue decomposition →
issues/*.mdpublished to tracker. - Single-session (no PRD,
task_breakdownphase): lightweight → singletasks.mdin.scratch/<slug>/, no tracker publish.
Process
- Context — conversation or fetched issue/PR from
docs/agents/issue-tracker.md. For single-session, usetech-spec.md+NOTES.mdas input. - Explore (optional) — codebase, domain vocabulary, prefactor opportunities.
- Draft slices — title, blocked-by, user stories covered. Prefactor slices first.
- Quiz user — granularity, dependencies, merge/split. Iterate until approved.
- Publish — dependency order;
ready-for-agentunless told otherwise. Don't close parent. For single-session, writetasks.mdto.scratch/<slug>/.
Single-session two-phase breakdown (task_breakdown phase)
When in task_breakdown phase (single-session), run as two sub-phases with a human checkpoint between:
Phase 1 — parent tasks (3–5 items)
- Draft coarse-grained parent tasks from
tech-spec.md+NOTES.md - Each parent task is one demoable vertical slice
- Present to user: confirm, reorder, merge, or split before proceeding
Phase 2 — sub-task expansion (only after user confirms parent tasks)
- Expand each parent task into concrete sub-tasks with explicit
blocked_bydependencies - Compute waves via topological sort
- Write
tasks.mdwith YAML frontmatter
Issue template
Parent — link if applicable.
What to build — end-to-end behavior, not layer checklist.
Acceptance criteria — checkboxes.
Blocked by — issue refs or "None".
tasks.md template (single-session)
Include YAML frontmatter for structured dependency tracking:
---
tasks:
- id: t1
title: "Add WorkspacePaths dataclass"
blocked_by: []
- id: t2
title: "Wire workspace_paths() resolver"
blocked_by: [t1]
- id: t3
title: "Update path helpers to use WorkspacePaths"
blocked_by: [t1]
- id: t4
title: "Integration tests"
blocked_by: [t2, t3]
waves:
- [t1]
- [t2, t3]
- [t4]
---
# Tasks: <slug>
## Wave 1
- [ ] **t1**: Add WorkspacePaths dataclass — <end-to-end behavior>. Blocked by: None
## Wave 2
- [ ] **t2**: Wire workspace_paths() resolver — <end-to-end behavior>. Blocked by: t1
- [ ] **t3**: Update path helpers to use WorkspacePaths — <end-to-end behavior>. Blocked by: t1
## Wave 3
- [ ] **t4**: Integration tests — <end-to-end behavior>. Blocked by: t2, t3
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.
- 5d ago First seen · 87 lines · 21 tokens per session scan A 0dded44feb68
to-issues is a skill published in the GitHub repository yugasun/aiops (4 stars, last pushed 17d ago), licensed Apache-2.0. It adds 21 tokens to every session and 771 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-31.
Other skills, from other repositories
hashiiiii-images
Use this skill to create project images, especially flat geometric images with a dark background and one accent color.
hashiiiii-pull-request
Use this skill to create or edit a GitHub pull request with the repository template or the default structure.
hashiiiii-issues
Use this skill to create or edit GitHub issues with a consistent body structure.
hashiiiii-git
Use this skill to name a Git branch or write a commit message.
hashiiiii-locale
Use this skill to set or change locale preferences for a user, project, or local Git worktree.
new
Create a new project to start development quickly.