Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/egregore-labs/egregore/main/.claude/skills/issue/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/issue)<a href="https://agentmods.dev/skills/egregore-labs/egregore/issue"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/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/egregore-labs/egregore/issue"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/issue.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.00054 | $0.03387 |
| Opus 5.5 | $0.00022 | $0.01355 |
| Sonnet 5.5 | $0.00011 | $0.00677 |
| Haiku 4.5 | $0.00005 | $0.00339 |
Grade A, and why
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 24d 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue
Optional Jev triage
Automatically use the shared advisor before freezing an internal report draft
only when issues.backend is github, issues.repo is configured and
issues.triage.enabled is true. Do not automatically invoke it for support
report or public upstream routes. Explicit selected-report triage is available
with either issue backend and those routes under the same separate provider
opt-in. The advisor never changes an issue.
TypeSafe AI receives the selected title, description and any explicitly supplied
environment/evidence. Do not include transcripts, unrelated memory or internal
request markers. Before enabling this adapter, disclose that separate provider
and its data handling, then record the user's
opt-in in egregore.json.issues.triage. Existing GitHub/support consent alone
does not opt in. Once enabled, do not repeat that setup question for each report.
The credential is TYPESAFE_API_KEY in the process environment or project
.env; never print it. Configuration example:
{"enabled": true, "provider": "typesafe", "model": "jev-1.13.0"}
Use '{title}' and '{report}' for the selected report text; escape an
embedded single quote as '\''. A local preview needs no provider call:
bash bin/issue.sh triage --title '{title}' --description '{report}' --preview
When opted in, state briefly that TypeSafe is processing the selected report fields, then request the advisory:
bash bin/issue.sh triage --title '{title}' --description '{report}'
Pass --kind, --area or --severity only for explicit user selections.
Render useful suggestions and uncertainties in plain language, not raw JSON.
Read draft_fields together with draft_field_sources: label advisor values
as Jev suggestions, human values as confirmed, and default values as defaults.
On abstention, bug, other and normal are filing defaults, not Jev advice.
Preserve confirmed_fields. Present impact suggestions for human confirmation;
severity remains human-selected or the unconfirmed normal default. Ownership
also remains a human decision. Confidence is not a probability that a suggestion
is correct.
Missing fields are optional follow-up signals: ask only when the answer changes
the next action, and keep incomplete reports fileable.
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.
- 24d ago Changed · -523 lines · +5 tokens per session scan C → A 38b9b966d468
- 1mo ago First seen · 874 lines · 49 tokens per session scan C 32a17b9ad0e8
issue is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 54 tokens to every session and 3,387 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
parallel-investigation
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist…
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
feedback
Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.