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 NOMARJ/sigil --skill devops-teamsgit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/devops-teams)<a href="https://agentmods.dev/skills/nomarj/sigil/devops-teams"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/devops-teams/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/nomarj/sigil/devops-teams"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/devops-teams.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.00000 | $0.01696 |
| Opus 5.5 | $0.00000 | $0.00678 |
| Sonnet 5.5 | $0.00000 | $0.00339 |
| Haiku 4.5 | $0.00000 | $0.00170 |
Grade A, and why
devops-teams 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Agent Teams
Skill for orchestrating Claude Code agent teams on DevOps tasks with NOMARK discipline.
NOMARK Integration
Teams are the execution model. NOMARK is the discipline. Every teammate follows NOMARK.
Pipeline Decision Points
/think (solo)
│
/plan (solo + code-explorer, or team-explore for multi-component)
│
├─ Single component? → /build (solo NOMARK)
├─ Multi component? → /team-build (parallel, each teammate follows NOMARK)
│
/verify or /team-review
│
/commit → /pr
When to Use Teams vs Solo
| Signal | Use | Command |
|---|---|---|
| All stories touch same files | Solo | /build |
| Stories span 2+ components | Team | /team-build |
| Bug in one component | Solo | /bugfix |
| Bug spans infra + code + workflow | Team | /team-bugfix |
| Pre-PR check, single component | Solo | /verify |
| Pre-PR check, multi component | Team | /team-review |
| Deployment readiness | Team | /team-deploy |
When to Use Teams
Use agent teams when the task involves parallel, independent work across multiple components:
| Scenario | Team Structure |
|---|---|
| Infrastructure + MCP changes | infra-specialist + mcp-developer |
| Security audit | security-reviewer + infra-specialist + mcp-developer |
| New integration (end-to-end) | workflow-builder + mcp-developer + qa-verifier |
| Major refactor | mcp-developer + qa-verifier + security-reviewer |
| Full release prep | all 5 roles |
| Cross-component bug | relevant specialists + qa-verifier |
Story-to-Teammate Routing
When /team-build analyzes PRD stories, route by file ownership:
What ships with it
1 file 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.
- 1mo ago First seen · 190 lines · 0 tokens per session scan A 4884ba81b88b
devops-teams is a skill published in the GitHub repository NOMARJ/sigil (6 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,696 tokens. 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-09-04.
Other skills, from other repositories
sftp-cc
A natural-language SFTP tool for uploading local project files to a remote server. SFTP is a secure way to transfer files, and this tool supports incremental uploads, private-key binding, and permission fixes.
memory
Retrieve relevant durable BB memories or save verified knowledge useful to future threads.
thread-list
Inspect or change the sidebar thread list's layout preferences: organization mode, sort, section order, hidden groups, collapsed groups, and thread row actions.
workflows
Author or run durable BB workflows when the user requests workflow execution or multi-agent orchestration.
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
url
Fetch and extract text from web URLs.