Borrowing it
Nothing to install: this file belongs to allenhutchison/obsidian-gemini. 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/allenhutchison/obsidian-gemini/master/.agents/skills/triage-issues/SKILL.mdgit clone --depth 1 https://github.com/allenhutchison/obsidian-geminiWrote 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/allenhutchison/obsidian-gemini/triage-issues)<a href="https://agentmods.dev/skills/allenhutchison/obsidian-gemini/triage-issues"><img src="https://agentmods.dev/badge/skills/allenhutchison/obsidian-gemini/triage-issues/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/allenhutchison/obsidian-gemini/triage-issues"><img src="https://agentmods.dev/badge/skills/allenhutchison/obsidian-gemini/triage-issues.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.00116 | $0.02019 |
| Opus 5.5 | $0.00046 | $0.00808 |
| Sonnet 5.5 | $0.00023 | $0.00404 |
| Haiku 4.5 | $0.00012 | $0.00202 |
Grade A, and why
triage-issues 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 2mo 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage open issues
obsidian-gemini's issue tracker accumulates issues from users, contributors, and the maintainer. Many land without labels, which makes filtering and reporting harder later. This skill works through the unlabeled backlog and applies labels from the repo's existing label vocabulary based on the issue's content.
This skill is deliberately conservative:
- It only applies labels — never closes, reassigns, links, or comments.
- It only uses labels that already exist in the repo.
- When the issue is ambiguous, it abstains rather than guess.
- It is safe to run repeatedly; previously-labeled issues are skipped automatically.
Workflow
1. Load the repo's label vocabulary
gh label list --repo allenhutchison/obsidian-gemini --limit 100 \
--json name,description
Hold this list in working memory. Do not invent labels. If the issue genuinely needs a label that doesn't exist, flag it in the report and let the human decide whether to create it (label creation is out of scope for this skill).
The repo currently has two practical label families. Check the live list each run; the exact set drifts:
- General intent:
bug,enhancement,documentation,question,help wanted,good first issue,duplicate,invalid,wontfix - Area:
agent-config,architecture,chat-ux,file-context,tool-execution,models,quick-win,epic - Auto-applied (do not apply by hand):
codex,automated,dependencies,javascript,github_actions— these are set by automation and labelling them manually adds noise.
2. List unlabeled open issues
gh issue list --repo allenhutchison/obsidian-gemini \
--state open --search "no:label" \
--limit 100 \
--json number,title,body,author,createdAt
If the result is empty, write a one-line "no unlabeled issues" report and stop. This is the common case on a well-tended tracker.
If the count is unusually large (>20 in a single run), still process them, but flag the pile-up in the report — it usually means triage hasn't run recently, or new issues are arriving faster than expected.
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.
- 2mo ago First seen · 135 lines · 116 tokens per session scan A ede6150a3e85
triage-issues is a skill published in the GitHub repository allenhutchison/obsidian-gemini (533 stars, last pushed today), licensed MIT. It adds 116 tokens to every session and 2,019 once invoked, about $0.0005 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.