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 fpindej/netrock --skill create-issuegit clone --depth 1 https://github.com/fpindej/netrockWrote 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/fpindej/netrock/create-issue)<a href="https://agentmods.dev/skills/fpindej/netrock/create-issue"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/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/fpindej/netrock/create-issue"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/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.00012 | $0.00292 |
| Opus 5.5 | $0.00005 | $0.00117 |
| Sonnet 5.5 | $0.00002 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
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 1mo 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.
What it actually says
Creates a GitHub issue.
Infers type, scope, labels, and whether to split into sub-issues from context. Asks only if the user hasn't described what needs to be done.
Steps
- Determine title in Conventional Commit format:
type(scope): description- Infer type (
feat,fix,refactor,chore,docs) and scope from the description
- Infer type (
- Write a body: problem, proposed approach, affected files/areas
- Apply labels - all that fit:
backend,frontend,security,feature,bug,documentation - If the work crosses stack boundary (backend + frontend) or has multiple independent deliverables, split into sub-issues:
gh issue create --title "..." --body "..." --label "..." # Get sub-issue numeric ID gh api --method GET /repos/{owner}/{repo}/issues/{sub_number} --jq '.id' # Link to parent gh api --method POST /repos/{owner}/{repo}/issues/{parent_number}/sub_issues --field sub_issue_id={id} - For small, tightly coupled changes - create a single issue (don't over-split)
- Report created URL(s)
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.
- 1mo ago First seen · 26 lines · 12 tokens per session scan A 74393b1db424
create-issue is a skill published in the GitHub repository fpindej/netrock (234 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 292 once invoked, about $0.0000 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
setup-husky-dotnet
Use when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically.
github
GitHub operations: list/create issues, PRs, check CI, manage repos. Requires GHTOKEN.
he-ship
Deliver a verified build through a task branch and PR, check the intended remote result, and clean up the completed task safely. Use for PR creation, shipping, merging or release/deployment requests; skip planning, implementation and review-only work.
gitlab_read
Read access: projects, issues, MRs, files, pipelines, members.
gitlab-guide
Use when managing GitLab tickets/work items, issue-board kanban, merge-request delivery/review, durable issue or MR context notes, or native CI/policy enforcement on GitLab.com, Self-Managed, or Dedicated. Triggers on glab issue, issue links, work items, board lists/status moves, glab mr, Notes/discussions, approvals…
speckit-chore-fetch
Load an existing GitHub issue into the chore workflow and seed a triage draft.