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 ivanshamaev/de-agent-skills --skill dataops_github_actions_optimizergit clone --depth 1 https://github.com/ivanshamaev/de-agent-skillsWrote 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/ivanshamaev/de-agent-skills/dataops_github_actions_optimizer)<a href="https://agentmods.dev/skills/ivanshamaev/de-agent-skills/dataops_github_actions_optimizer"><img src="https://agentmods.dev/badge/skills/ivanshamaev/de-agent-skills/dataops_github_actions_optimizer/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/ivanshamaev/de-agent-skills/dataops_github_actions_optimizer"><img src="https://agentmods.dev/badge/skills/ivanshamaev/de-agent-skills/dataops_github_actions_optimizer.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.00083 | $0.02360 |
| Opus 5.5 | $0.00033 | $0.00944 |
| Sonnet 5.5 | $0.00017 | $0.00472 |
| Haiku 4.5 | $0.00008 | $0.00236 |
Grade A, and why
dataops-github-actions-optimizer 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 331 lines · 83 tokens per session scan A 9cb5e0ef89f4
dataops-github-actions-optimizer is a skill published in the GitHub repository ivanshamaev/de-agent-skills (21 stars, last pushed 5mo ago), with no licence file. It adds 83 tokens to every session and 2,360 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-30.
Other skills, from other repositories
agentsop-regression-gate
Build a held-out eval set, run it on every prompt/model change, and block regressions in CI. An LM change is a code change — gate it with a test suite (eval set + metric + threshold). Cross-framework SOP not surfaced by any single base skill.
deploy-pipeline-runbook
Use when a release spans multiple systems or vendors, order of operations matters with rollback planned up front, or a failed step in one system could corrupt state in a downstream system.
github-ci-failure-triage
Use when a GitHub PR shows failing checks and a clean failure readout is needed before changing any code.
pr-review-ci-loop
Use when a pull request needs one bounded review and CI triage cycle with explicit approval before edits or remote writes.
ci-failure-readout
Use when a CI pipeline has failed and the real error must be extracted from thousands of lines of noisy logs.
pre-release-verification
Use when a release candidate needs final checks before tagging, publishing, or production deployment.