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 agentmods add skills/adrian-d-hidalgo/nestjs-mcp-server/github-issuesnpx skills add adrian-d-hidalgo/nestjs-mcp-server --skill github-issuesgit 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.svg" alt="Measured on agentmods" 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 | $0.00088 | $0.10529 |
| Opus 5 | $0.00044 | $0.05264 |
| Sonnet 5 | $0.00018 | $0.02106 |
| Haiku 4.5 | $0.00009 | $0.01053 |
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 4d 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 — 709 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.
Mode X — technical debt also has no form. It is a Mode T issue with a mandatory
Closure condition; see the Debt pattern below.
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.
- 4d 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 (38 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 10,529 once invoked, about $0.0004 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
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.