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-create-issuegit 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-create-issue)<a href="https://agentmods.dev/skills/aliengiraffe/vigilante/vigilante-create-issue"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-create-issue/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-create-issue"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-create-issue.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.00025 | $0.02456 |
| Opus 5 | $0.00013 | $0.01228 |
| Sonnet 5 | $0.00005 | $0.00491 |
| Haiku 4.5 | $0.00003 | $0.00246 |
Grade A, and why
vigilante-create-issue 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 10d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vigilante Create Issue
Overview
Use this skill when a human wants to write or refine a GitHub issue that Vigilante will later implement. The default goal is to turn a vague request into an issue with enough behavioral detail, constraints, and verification criteria for a headless coding agent to execute safely, then create that issue on GitHub. If creation is not possible, fall back to returning a ready-to-file issue body. The goal is not to design the full solution for them.
Outcome
Produce a GitHub issue that is:
- classified as a
feature,bug, ortaskbefore the draft is finalized - specific about the problem and why it matters
- grounded in repository or product context
- explicit about expected behavior and non-goals
- realistic about implementation flexibility and hard constraints
- testable through concrete acceptance criteria
- clear about validation and regression coverage
- created on GitHub by default when the target repository can be resolved and
ghissue creation is available - returned as a polished Markdown draft only when the user explicitly asks for draft-only output or issue creation is blocked
Workflow
- Clarify the request before writing
- Identify the change the user actually wants.
- Ask for missing repository, product, or user context when it affects implementation.
- Separate required behavior from guesses or preferences.
- Classify the request before finalizing the issue body
- Decide whether the request is best treated as a
feature,bug, ortask. - Base the classification on the user's stated problem and desired outcome rather than implementation details.
- If the request is ambiguous, infer the most likely type and state briefly that the type was inferred.
- Use the selected type to decide which details are required in the issue body, not just to append a label.
- Resolve the target repository before finalizing output
- Prefer local git context first when the user is working inside a repository.
- Otherwise use an explicitly provided repository slug or URL.
- If the repository cannot be resolved confidently, say so briefly and fall back to returning the ready-to-file issue body instead of guessing.
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.
- 10d ago First seen · 209 lines · 25 tokens per session scan A ff4a016bba5f
vigilante-create-issue is a skill published in the GitHub repository aliengiraffe/vigilante (40 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 2,456 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-30.
Other skills, from other repositories
kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…
send-feedback
Explicit Codex workflow: Collect reviewed, sanitized rn-dev-agent feedback and create a GitHub issue only with user confirmation.
pipeline-conductor
Operating procedure for the kirocrew-pipeline-conductor agent - run one issue/PR pipeline on one repository as a supervised fleet. Auto-pick items, preflight every candidate to one deterministic claim verdict, stand up one worker session per item in a dedicated folder, probe them each cycle with one script call…
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
goal-ledger-conductor
Own a long-horizon goal end to end while tracking it in the work ledger - decompose it into items, stand up one session per item, read each worker's reported status as structured data rather than as a transcript, verify claims with the acceptance evaluator, and decide each next round until the goal is met or a stop…
feature-request
Conversational workflow for gathering user feedback and filing GitHub Issues on the Kiro Crew repository. Load when the user clicks "Request a Feature", wants to report a bug, or suggest an improvement.