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/fpindej/netrock/create-issuenpx skills add fpindej/netrock --skill create-issuegit clone --depth 1 https://github.com/fpindej/netrockWhat 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.00012 | $0.00292 |
| Opus 5 | $0.00006 | $0.00146 |
| Sonnet 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 2d 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.
- 2d ago First seen · 26 lines · 12 tokens per session scan A 74393b1db424
create-issue is a skill published in the GitHub repository fpindej/netrock (231 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 292 once invoked, about $0.0001 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
api-design
Guidelines for RESTful API design, endpoint naming conventions, and standardizing JSON responses.
python
Enforces FastAPI, Dependency Injection, and general Python coding standards based on the repository structure.
react
Guidelines for the React frontend, TanStack ecosystem, and React 19 standards. Use when modifying the UI.
react-testing
Frontend testing standards using Vitest, React Testing Library, and Playwright. Use when writing UI tests.
python-testing
Guidelines for Python testing using pytest and pytest-asyncio. Use when writing or debugging backend tests.
database-management
Standards for SQLAlchemy async models, PostgreSQL indexing, UTC datetimes, and Alembic migrations.