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/aiops-setupnpx skills add yugasun/aiops --skill aiops-setupgit 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/aiops-setup)<a href="https://agentmods.dev/skills/yugasun/aiops/aiops-setup"><img src="https://agentmods.dev/badge/skills/yugasun/aiops/aiops-setup.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.00042 | $0.00679 |
| Opus 5 | $0.00021 | $0.00340 |
| Sonnet 5 | $0.00008 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
aiops-setup 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aiops-setup
Scaffold per-repo config: issue tracker, triage labels, domain docs.
Modes
Silent bootstrap (from /aiops conductor)
When docs/agents/ is missing:
- Read repo-root
aiops.yamlif present — see aiops-yaml.md. - No yaml →
issue_tracker.kind: local, triage labels 1:1,domain.layout: single. Writedocs/agents/*without asking. - Yaml with
githuborgitlab→ seed matchingissue-tracker-*.md; apply yamlprs_as_triageand label overrides. No A/B/C questionnaire unless yaml is incomplete. - Update
CLAUDE.mdorAGENTS.md## Agent skillsblock (create section if missing; ask only if neither file exists).
Full setup (explicit /aiops-setup)
Interactive — explore, confirm one section at a time, then write. Use when switching tracker or restarting config.
Full setup process
1. Explore
Check: aiops.yaml, git remote, AGENTS.md / CLAUDE.md, CONTEXT.md, CONTEXT-MAP.md, docs/adr/, docs/agents/, .scratch/.
2. Ask (one section at a time)
Skip sections already satisfied by aiops.yaml — show yaml values and offer edit only.
A — Issue tracker: Only offer GitHub/GitLab in the questionnaire if user has no aiops.yaml and explicitly asks for remote tracker. Otherwise default local markdown.
B — Triage labels: Map five roles to tracker strings. Default 1:1.
C — Domain docs: Single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md).
D — Constitution: If CONSTITUTION.md does not exist at repo root, offer to generate one from constitution-template.md. Walk through each section (Testing, Code quality, Architecture, Performance, Security, Process) and ask the user to fill in project-specific principles. These are non-negotiable — referenced by every agent at every phase.
3. Confirm draft
Show ## Agent skills block + docs/agents/issue-tracker.md, triage-labels.md, domain.md for user edit.
What ships with it
8 files 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 · 55 lines · 42 tokens per session scan A ecc6ccc2d45b
aiops-setup is a skill published in the GitHub repository yugasun/aiops (4 stars, last pushed 15d ago), licensed Apache-2.0. It adds 42 tokens to every session and 679 once invoked, about $0.0002 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.
make_plan
For external plan request scenarios, guides the Agent to request a clear, actionable, step-by-step plan from a stronger Agent via listagents and chatwithagent, emphasizing that the plan is executed by the requester, not by the consulted Agent.