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/arpitexplores/skills-super/super-engineering-devopsnpx skills add arpitexplores/skills-super --skill super-engineering-devopsgit clone --depth 1 https://github.com/arpitexplores/skills-superWrote 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/arpitexplores/skills-super/super-engineering-devops)<a href="https://agentmods.dev/skills/arpitexplores/skills-super/super-engineering-devops"><img src="https://agentmods.dev/badge/skills/arpitexplores/skills-super/super-engineering-devops.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.1 | $0.00025 | $0.00375 |
| Opus 5 | $0.00013 | $0.00187 |
| Sonnet 5 | $0.00005 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
super-engineering-devops 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 5d 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
Super Engineering/DevOps
Overview
Build and run software with strong architecture, quality, and delivery practices.
User Intent Examples
- "Need help with DevOps & Deployment for my product/site."
- "Create a plan for Observability."
- "Audit or improve Full-Stack Engineering."
Workflow
- Clarify requirements, constraints, and success metrics.
- Select architecture and core tech stack.
- Design data models, APIs, and integration boundaries.
- Implement with tests and quality checks.
- Set up CI/CD and deployment strategy.
- Add observability and runbooks.
Minimal Intake Questions
- Primary goal or outcome
- Scope (pages, systems, teams, or timeframe)
- Constraints (tools, budget, timeline)
Output Format
- Architecture and design summary
- Implementation plan
- Test and QA plan
- CI/CD and deployment plan
- Observability checklist
Routing Map (Modules)
- DevOps & Deployment ->
references/modules/devops-deploy.md - Observability ->
references/modules/observability-engineer.md - Full-Stack Engineering ->
references/modules/senior-fullstack.md
Bundled References
references/modules/scripts/assets/agents/
Compatibility Notes
- If any module references slash commands or tool-specific paths, translate them into plain-language steps.
- Keep outputs platform-agnostic unless the user specifies a specific tool, stack, or agent.
Guardrails
- Do not claim performance gains without measurements.
- Keep testing requirements explicit.
- Prefer incremental delivery and rollback safety.
What ships with it
9 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.
- 5d ago First seen · 56 lines · 25 tokens per session scan A 9f0f3a460d12
super-engineering-devops is a skill published in the GitHub repository arpitexplores/skills-super (2 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 375 once invoked, about $0.0001 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
plans
Manage the plans/ spec-driven planning system. Use init to bootstrap plans/ in a project, sync to audit drift between plan files and git, new to create a plan file, update to refresh system files. Invoked as /plans:plans (plugin) or /plans (project-local).
markdown-ui-dsl
Create low-fidelity, text-based wireframes using the Markdown-UI Domain Specific Language (DSL).
orchestrate
You are operating with persistent memory. This skill defines how to maintain context across sessions.
agent-baton
多角色 AI 团队接力协作框架（BA / Arch / Dev / TechLead），通过 Markdown 文档在角色之间传递上下文，适用于需要结构化协作的中大型项目。当用户明确说"用 AgentBaton 初始化项目"/"启动 AgentBaton 框架"，或提到任一角色名（"BA 角色"/"Arch 角色"/"Dev 角色"/"TechLead 角色"/"TechLead Review"），或当前项目根目录已存在 config/roles/ 或 config/TEAMGUIDE.md 时，使用本 skill。不要用于：简单代码修改、bug 修复、单文件改动、代码探索、纯重构、与多角色协作无关的常规开发任务。.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.