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/vincenthopf/my-claude-code/huly-issuesnpx skills add vincenthopf/My-Claude-Code --skill huly-issuesgit clone --depth 1 https://github.com/vincenthopf/My-Claude-CodeWrote 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/vincenthopf/my-claude-code/huly-issues)<a href="https://agentmods.dev/skills/vincenthopf/my-claude-code/huly-issues"><img src="https://agentmods.dev/badge/skills/vincenthopf/my-claude-code/huly-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.1 | $0.00096 | $0.00425 |
| Opus 5 | $0.00048 | $0.00212 |
| Sonnet 5 | $0.00019 | $0.00085 |
| Haiku 4.5 | $0.00010 | $0.00042 |
Grade A, and why
huly-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 6d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
15 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.
- .env.example 366 B
- references/api-reference.md 6.0 KB
- scripts/auth.js 315 B runs code
- scripts/comment-add.js 1.2 KB runs code
- scripts/comments-list.js 1.3 KB runs code
- scripts/issues-create.js 2.1 KB runs code
- scripts/issues-delete.js 1.0 KB runs code
- scripts/issues-get.js 2.3 KB runs code
- scripts/issues-list.js 1.6 KB runs code
- scripts/issues-update.js 2.4 KB runs code
- scripts/lib/client.js 1.8 KB runs code
- scripts/package-lock.json 82 KB
- scripts/package.json 286 B
- scripts/projects.js 456 B runs code
- scripts/search.js 1.3 KB runs code
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.
- 6d ago First seen · 62 lines · 96 tokens per session scan A 16aabb64c2eb
huly-issues is a skill published in the GitHub repository vincenthopf/My-Claude-Code (135 stars, last pushed 5mo ago), with no licence file. It adds 96 tokens to every session and 425 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.