Borrowing it
Nothing to install: this file belongs to adrian-d-hidalgo/nestjs-mcp-server. 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/adrian-d-hidalgo/nestjs-mcp-server/main/.claude/skills/github-issues/SKILL.mdgit clone --depth 1 https://github.com/adrian-d-hidalgo/nestjs-mcp-serverWrote 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/adrian-d-hidalgo/nestjs-mcp-server/github-issues)<a href="https://agentmods.dev/skills/adrian-d-hidalgo/nestjs-mcp-server/github-issues"><img src="https://agentmods.dev/badge/skills/adrian-d-hidalgo/nestjs-mcp-server/github-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/adrian-d-hidalgo/nestjs-mcp-server/github-issues"><img src="https://agentmods.dev/badge/skills/adrian-d-hidalgo/nestjs-mcp-server/github-issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 233 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00088 | $0.10676 |
| Opus 5.5 | $0.00035 | $0.04270 |
| Sonnet 5.5 | $0.00018 | $0.02135 |
| Haiku 4.5 | $0.00009 | $0.01068 |
Grade A, and why
github-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 29d 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 — 723 lines — stays where its author put it; the contents beside it link to each section on GitHub.
There is one repository and one published package. There are no subrepos, so there is no work breakdown into sub-issues and no per-area split: one issue is one unit of work. If a requirement genuinely carries two independently-shippable deliverables, that is two issues — say so and ask; never fan out silently.
| Form | Mode | Title prefix | Labels the form applies | Use when |
|---|---|---|---|---|
bug_report.yml |
B — bug | [Bug]: |
bug, triage |
Defect in shipped code (any severity). |
feature_request.yml |
C — capability | [Feature]: |
enhancement, triage |
A capability the package should have but doesn't yet. |
refactoring.yml |
R — refactor | [Refactor]: |
refactor, triage |
Internal restructuring with no public-API change. |
security.yml |
S — security | [Security]: |
security, triage |
Non-critical vulnerability. Critical ones go to private disclosure, never here. |
documentation.yml |
D — docs | [Docs]: |
documentation, triage |
README / API reference / examples / TSDoc gaps. |
Mode T — technical task has no form. Dependency bumps, toolchain migrations, CI changes
and release-plumbing work are authored by hand under the chore label (that is why issues #119,
#113 and #112 carry no [Prefix]:). Its body shape lives here, in templates/task.md. Mode T
titles use a Conventional-Commits-shaped subject instead of a bracket prefix — e.g.
chore(deps): migrate to TypeScript 6 — matching what is already in the repository.
What ships with it
5 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.
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.
- 29d ago Changed · +14 lines 0406d9ca11f6
- 2mo ago First seen · 709 lines · 88 tokens per session scan A f56fa4c8a067
github-issues is a skill published in the GitHub repository adrian-d-hidalgo/nestjs-mcp-server (40 stars, last pushed 29d ago), licensed MIT. It adds 88 tokens to every session and 10,676 once invoked, about $0.0004 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.