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 yugasun/aiops --skill aiops-implementgit 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-implement)<a href="https://agentmods.dev/skills/yugasun/aiops/aiops-implement"><img src="https://agentmods.dev/badge/skills/yugasun/aiops/aiops-implement/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/yugasun/aiops/aiops-implement"><img src="https://agentmods.dev/badge/skills/yugasun/aiops/aiops-implement.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.00030 | $0.00770 |
| Opus 5.5 | $0.00012 | $0.00308 |
| Sonnet 5.5 | $0.00006 | $0.00154 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
aiops-implement 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aiops-implement
Implement from PRD, issue brief, or tech-spec. Not for grill/alignment — lean active only while writing code.
Invoked by Flow Conductor delivery phase (builder agent). Update flow.state.yaml → delivery_sub_phase as you progress.
Preconditions
- Issue brief or
issues/<current>AC, ortech-spec.md+NOTES.md DESIGN_REVIEW.mdAPPROVE when design review ran in this flow- If
/prototyperan:VERDICT.mdbefore absorbing prototype learnings
Impact analysis (before implement)
If graphify-out/graph.json exists, tell the user "查询代码图谱评估修改影响面" then query /code-graph query impact <target-file> before writing code to understand the blast radius. Log affected modules in the journey context so the builder knows what might break.
Orchestration (hard gates — fixed order)
Run sub-phases in order. Do not skip unless user explicitly exempts a step (e.g. mechanical fix → skip new tests).
| Sub-phase | delivery_sub_phase |
Who | Skill / action | Gate to advance |
|---|---|---|---|---|
| 1 | implement |
builder | lean ladder + write code | Tests for changed behaviour pass |
| 2 | implement |
builder | /tdd at public interfaces |
Red-green on agreed surface |
| 3 | prune |
quality-auditor | /prune on diff |
Findings listed or "Lean already" |
| 4 | review |
code-reviewer | /review vs NOTES/tech-spec/issue |
REVIEW.md APPROVE |
| 5 | ready_for_commit |
— | Set journey gate ready_for_commit |
User may ask gitops to ship |
Record in journey gates_satisfied: prune_done, review_approve, ready_for_commit.
File size
If any file you touch approaches 500 lines, invoke /file-refactor before advancing to prune — split per that skill (types → utils → hooks → sub-components). Skip only when the user exempts or the file is intentionally monolithic.
Wave-based execution (when tasks.md has frontmatter)
When .scratch/<slug>/tasks.md contains YAML frontmatter with waves:, execute tasks wave by wave:
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 · 63 lines · 30 tokens per session scan A 9e99a34eebd0
aiops-implement is a skill published in the GitHub repository yugasun/aiops (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 770 once invoked, about $0.0001 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
speq-implement
Orchestrate implementation of a reviewed plan: task breakdown, TDD sub-agents, code review, and verification report. Use when the user asks to implement, build, or execute a plan under specs/plans/ — after /speq-plan, before /speq-record. Arg: .
speq-code-guardrails
TDD cycle and code quality guardrails — failing-test-first, evidence, dependency, error-handling, and test-quality rules. Used by speq implementer and reviewer agents during a speq implement run. Not for general coding.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
hashiiiii-zig
Use when writing, editing, or reviewing Zig implementation, tests, build files, or CI.
cf-tdd
Gate before writing production code — direct implementation by default, TDD (RED→GREEN→REFACTOR) with --add-tests or config tdd: true. TRIGGER — any new feature, implementation, or refactor: "implement this", "build this feature", "create a function", "add a new endpoint", "write the implementation", "refactor this"…
testing-expert
Ultimate Kotlin testing skill. Use this whenever writing, reviewing, or debugging ANY Kotlin test — unit, integration, property-based, or coroutine. Covers TDD (RED/GREEN/REFACTOR), Kotest + MockK + Kover, anti-pattern detection, and four-pillar quality framework. Triggers on: write a test, add coverage, why is this…