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 simota/agent-skills --skill vigilgit clone --depth 1 https://github.com/simota/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/simota/agent-skills/vigil)<a href="https://agentmods.dev/skills/simota/agent-skills/vigil"><img src="https://agentmods.dev/badge/skills/simota/agent-skills/vigil/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/simota/agent-skills/vigil"><img src="https://agentmods.dev/badge/skills/simota/agent-skills/vigil.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.00037 | $0.05530 |
| Opus 5 | $0.00018 | $0.02765 |
| Sonnet 5 | $0.00007 | $0.01106 |
| Haiku 4.5 | $0.00004 | $0.00553 |
Grade C, and why
vigil scanned grade C with 1 finding 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 6d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- CAPABILITIES_SUMMARY: - detection_rule_design: Design Sigma rules, YARA rules, and SIEM queries for threat detection - detection_coverage_mapping: Map detection rules to MITRE ATT&CK techniques and identify coverage How it starts
The opening of the file, as written. The whole thing — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vigil
Detection engineering agent that builds the defensive sensor network. Designs detection rules, maps coverage gaps, hunts threats proactively, and validates that attacks are actually caught. The Blue Team counterpart to Breach's Red Team.
"An undetected attack is an undefended system. Vigil ensures nothing passes unseen."
What ships with it
12 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.
- _common 10 B
- reference/_common 13 B
- reference/autorun-schema.md 900 B
- reference/beacon 12 B
- reference/detection-as-code.md 13 KB
- reference/detection-patterns.md 13 KB
- reference/handoffs.md 3.0 KB
- reference/ioc-threat-intel.md 8.5 KB
- reference/mend 10 B
- reference/playbook-incident-response.md 9.5 KB
- reference/snort-network-detection.md 7.1 KB
- reference/triage 12 B
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.
- 6d ago First seen · 329 lines · 37 tokens per session scan C c8db583cb0cd
vigil is a skill published in the GitHub repository simota/agent-skills (76 stars, last pushed 7d ago), licensed MIT. It adds 37 tokens to every session and 5,530 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
fix-failing-pipelines
This skill should be used when the user asks to "fix pipelines", "fix CI", "check staging pipelines", "fix failing workflows", "fix failing actions", or wants to find and fix failing GitHub Actions workflows on the staging branch of the babysitter repo.
ci-troubleshoot
Diagnose failed GitHub Actions runs for pi-agent-dashboard: the 10-file workflow taxonomy, the release pipeline, known failure modes, and how to read gh run logs and retrigger jobs. Use when a CI run is red, a release is stuck, a workflow won't dispatch, or you need to know which workflow does what. See release-cut to…
release-readiness-check
Verify all prerequisites are met before a release by checking PRs, CI/CD status, environment health, and blocking issues across GitHub, ArgoCD, and Jira. Use before cutting a release, deploying to production, or during release planning.
tmux-layout
Use this skill when the operator wants a prepared tmux visualization layout for the session's side-channels (STATE.md tail, CI-watch, events.jsonl tail). Renders a 4-pane default layout or debug layout. Read-only side-channel observability — the coordinator chat stays in the operator's original terminal. Trigger…
principle-non-blocking-waits
Requires resumable waits for external state. Apply when waiting on CI, reviewers, deployments, or rate limits.
starfleet-github
GitHub PR/CI/backport interaction via starfleetctl (read-only + mutating commands, PR claims, backports). Load when checking PR status/CI, claiming a PR branch, submitting or repairing a PR, or backporting.