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 gitopsgit 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/gitops)<a href="https://agentmods.dev/skills/yugasun/aiops/gitops"><img src="https://agentmods.dev/badge/skills/yugasun/aiops/gitops/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/gitops"><img src="https://agentmods.dev/badge/skills/yugasun/aiops/gitops.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.00047 | $0.00486 |
| Opus 5.5 | $0.00019 | $0.00194 |
| Sonnet 5.5 | $0.00009 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
gitops 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.
What it actually says
Gitops
Git version control operations for the aiops delivery chain.
Operations
sync
Pull latest from remote. Default strategy: rebase.
git pull --rebase
If merge conflict: report to user, do not auto-resolve.
status
Show current working tree state.
git status
git diff --stat
stage
Stage files for commit. Supports selective staging.
git add <files>
commit
Create commit with Conventional Commits message.
Format:
<type>(<scope>): <subject>
<body>
Refs: .scratch/<feature-slug>/
Types: feat | fix | refactor | test | docs | chore
Message generation:
- Read
.scratch/<feature>/NOTES.mdfor design context - Read
.scratch/<feature>/REVIEW.mdto confirm review passed - Scope = feature-slug or module name
- Subject = imperative, lowercase, no period
- Body = reference upstream artifacts for traceability
Pre-commit checks:
- All blocking REVIEW.md findings resolved
- No untracked .scratch files in commit (add to .gitignore if needed)
push
Push to remote. Requires user confirmation.
git push origin <branch>
branch
Branch management: create, switch, list.
git checkout -b <branch> # create + switch
git checkout <branch> # switch
git branch # list
Flow
sync— pull lateststatus— review changesstage— select filescommit— with generated messagepush— after user confirms
Constraints
- Never modify code files
- Never auto-resolve merge conflicts
- Always confirm with user before push
- Commit message must reference .scratch artifacts when available
- If
.scratch/<feature>/REVIEW.mdexists and verdict is REQUEST_CHANGES, block commit and report
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 · 101 lines · 47 tokens per session scan A 1f02ba85310c
gitops is a skill published in the GitHub repository yugasun/aiops (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 486 once invoked, about $0.0002 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
hashiiiii-git
Use this skill to name a Git branch or write a commit message.
commit
Skill "commit" from clacky-ai/openclacky, covering smart commit skill, critical requirement: single-line commits only, core philosophy, usage and process steps.
devops-pipeline
Configure pre-commit hooks and lean GitHub Actions for shift-left quality assurance. Use when adding or auditing CI/CD to maximize local test coverage and minimize CI cost. Skip for Terraform/K8s, deployment pipelines, or non-GitHub CI providers.
auto-push
Generate a commit message, stage all changes, and push to remote after scanning for secrets, large files, and protected-branch risks. Skip for opening PRs, code review, or cutting releases/tags.
github
Manage the full GitHub workflow from the terminal — auth, issues, pull request lifecycle (branch/commit/open/CI/merge), code review, and repo management. Uses the gh CLI when present, with a git + REST API fallback. Use when asked to "open a PR", "create an issue", "review this PR", "check CI", "list issues".
speq-git-discipline
Read-only git guardrails. No history writes, verify changes before completing. Used by speq agents during a speq run. Not for general git work. The headless orchestrators speq-plan-pr and speq-implement-pr use /speq-git-operations instead.