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 martinholovsky/SOTA-skills --skill sota-devsecopsgit clone --depth 1 https://github.com/martinholovsky/SOTA-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/martinholovsky/sota-skills/sota-devsecops)<a href="https://agentmods.dev/skills/martinholovsky/sota-skills/sota-devsecops"><img src="https://agentmods.dev/badge/skills/martinholovsky/sota-skills/sota-devsecops/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/martinholovsky/sota-skills/sota-devsecops"><img src="https://agentmods.dev/badge/skills/martinholovsky/sota-skills/sota-devsecops.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.00205 | $0.02720 |
| Opus 5 | $0.00102 | $0.01360 |
| Sonnet 5 | $0.00041 | $0.00544 |
| Haiku 4.5 | $0.00020 | $0.00272 |
Grade A, and why
sota-devsecops 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 yesterday.
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
Licensed CC-BY-4.0
The repository is licensed CC-BY-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What ships with it
10 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.
- rules/01-pipeline-security.md 27 KB
- rules/02-provenance-signing.md 16 KB
- rules/03-dependencies.md 19 KB
- rules/04-build-containers.md 14 KB
- rules/05-analysis-gates.md 13 KB
- rules/06-iac-deployment.md 16 KB
- rules/07-runtime-ops.md 18 KB
- rules/08-registry-security.md 19 KB
- rules/09-gates-that-hold.md 25 KB
- rules/10-inert-dependencies.md 16 KB
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.
- yesterday Changed 8eb41479313a
- 2d ago Changed · +2 lines 1828d91e3534
- 10d ago First seen · 120 lines · 205 tokens per session scan A 6598c89568ea
sota-devsecops is a skill published in the GitHub repository martinholovsky/SOTA-skills (18 stars, last pushed today), licensed CC-BY-4.0. It adds 205 tokens to every session and 2,720 once invoked, about $0.0010 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-30.
Other skills, from other repositories
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
ci-all
Full CI pipeline: run local tests, type check, push branch, and return the pipeline URL. The only command you need before opening a PR.
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).
ci-status
Show current pipeline status for the active branch (GitLab CI or GitHub Actions).
yds-data-validation
Inspect a project's data for correctness and produce a read-only validation report — record counts, NULL rates, value distribution, uniqueness, referential integrity, format validity, and sampled evidence rows. Data is read only from the project's own test fixtures/seed data or from an explicitly configured…
yds-software-evaluation
Evaluate code quality across five pillars (Architecture, Reliability, Observability, Security, DX) and produce a 1-10 scorecard with a strategic improvement roadmap. Use when you want a comprehensive quality review of a directory or module. Triggers on requests like "evaluate code quality", "review architecture"…