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 aliengiraffe/vigilante --skill vigilante-issue-implementation-on-github-actionsgit clone --depth 1 https://github.com/aliengiraffe/vigilanteWrote 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/aliengiraffe/vigilante/vigilante-issue-implementation-on-github-actions)<a href="https://agentmods.dev/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-github-actions"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-github-actions/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/aliengiraffe/vigilante/vigilante-issue-implementation-on-github-actions"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-github-actions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.01039 |
| Opus 5.5 | $0.00020 | $0.00416 |
| Sonnet 5.5 | $0.00010 | $0.00208 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
vigilante-issue-implementation-on-github-actions 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vigilante GitHub Actions Issue Implementation
Focus
- Read the prompt for detected tech stacks, process hints, and security guidance before changing workflow files.
- Keep changes scoped to the issue and do not broaden into unrelated workflow or repository changes.
- Treat
.github/workflows/as a security-sensitive surface. Every workflow edit should consider permissions, secret exposure, and supply-chain risk.
Workflow File Conventions
- Use
.ymlor.yamlconsistently with the repository's existing convention. Do not mix extensions within the same repository. - Validate workflow syntax before committing. Use
actionlintwhen it is available in the repository or installed locally. Ifactionlintis not available, note its absence and continue — do not fabricate output. - Keep workflow files readable: use clear job and step names, add inline comments for non-obvious logic, and prefer reusable workflows or composite actions over duplicated step blocks.
Pinned Actions
- Pin third-party actions to full commit SHAs, not mutable tags or branch references. Example:
uses: actions/checkout@<full-sha>with a trailing version comment. - When updating an action version, verify the new SHA corresponds to a reviewed release or tag.
- First-party GitHub actions (
actions/*) should also be pinned to SHAs for consistency and supply-chain safety. - When adding a new third-party action, prefer well-maintained actions with high community adoption. Avoid actions that request broad permissions or lack clear provenance.
Least-Privilege Permissions
- Always declare a top-level
permissions:block in workflow files. Default to the most restrictive set needed. - Use read-only
contents: readunless the workflow must write (e.g., creating releases, pushing tags, commenting on PRs). - Scope token permissions per job when different jobs need different access levels.
- Never use
permissions: write-allor leave permissions unspecified, which defaults to broad access in some repository configurations.
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 · 60 lines · 49 tokens per session scan A 4cd37d11728b
vigilante-issue-implementation-on-github-actions is a skill published in the GitHub repository aliengiraffe/vigilante (41 stars, last pushed 4d ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,039 once invoked, about $0.0002 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
babysit
Use when a user asks to babysit, monitor, keep checking, keep an eye on, or report when a pull request, CI run, ticket, deployment, or other changing target reaches an outcome.
deploying-to-staging-environment
Use when deploying changes to staging across relay, relay-dashboard, and relay-cloud repos - coordinates multi-repo branch syncing using git worktrees, automatically triggers staging deployments via GitHub Actions.
rn-device-control
This skill should be used when the user asks to "control the simulator", "take a screenshot", "boot the emulator", "install the app", "read UI hierarchy", "manage device state", "open a deep link", "grant permissions", "stream native logs", "disable animations", "change device locale", or needs guidance on xcrun…
rn-feature-development
This skill should be used when building any new feature in a React Native or Expo app, or when the $rn-dev-agent:rn-feature-dev command runs. Triggers on "build a feature", "add X to the app", "implement Y", "create a new screen", "rn-feature-dev", "feature development", "build me X", "add a screen", "wire up this…
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
rn-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — read project instructions and the declared package manager, inventory sessions/Metro/devices read-only, establish one exclusive simulator/emulator via typed session actions, apply and verify package integration and…