Borrowing it
Nothing to install: this file belongs to hiero-ledger/solo. 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/hiero-ledger/solo/main/.claude/skills/solo-create-issue/SKILL.mdgit clone --depth 1 https://github.com/hiero-ledger/soloWrote 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/hiero-ledger/solo/solo-create-issue)<a href="https://agentmods.dev/skills/hiero-ledger/solo/solo-create-issue"><img src="https://agentmods.dev/badge/skills/hiero-ledger/solo/solo-create-issue.svg" alt="Measured on agentmods" 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.00058 | $0.02534 |
| Opus 5 | $0.00029 | $0.01267 |
| Sonnet 5 | $0.00012 | $0.00507 |
| Haiku 4.5 | $0.00006 | $0.00253 |
Grade A, and why
solo-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 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.
How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solo Create Issue
Parse the user's request and create a GitHub issue in hiero-ledger/solo with full project
metadata using one Bash tool call that runs all GraphQL mutations sequentially in a single
script. All IDs are pre-resolved — no lookup calls needed.
Step 1 — Parse the user's request
Extract the following from the user's natural-language description:
| Field | How to determine |
|---|---|
| Title | Synthesize a clear, action-oriented title (≤ 80 chars) |
| Body | Write a structured body (see Body Format below) |
| Issue Type | Explicit mention or infer from context (default: Task) |
| Priority | Explicit P0/P1/P2 or infer from urgency language (default: P1) |
| Status | Explicit mention or default to Ready; use Backlog when the issue has unresolved blockers |
| Labels | Always include the priority label; add others based on content |
| Parent issue | If the user mentions a parent epic/initiative, capture its node ID for addSubIssue |
Body Format
## Overview
<2-4 sentence summary of the goal and motivation>
## Sub-Tasks
- [ ] Sub-task one
- [ ] Sub-task two
## Prerequisites
- [ ] Any blockers or dependencies (omit section if none)
### Dependencies
- [ ] requires #N ← issues this one depends on
- [ ] required by #N ← issues that depend on this one
## References
- [Link text](url) — one line per reference (omit section if none)
Step 2 — Resolve IDs from the tables below
Repository (fixed)
| Name | ID |
|---|---|
Repo hiero-ledger/solo |
R_kgDOLMTWdQ |
Issue Types
| Type | ID |
|---|---|
| Task | IT_kwDOCq2Q984BY34v |
| Bug | IT_kwDOCq2Q984BY34w |
| Feature | IT_kwDOCq2Q984BY34x |
| Epic | IT_kwDOCq2Q984BhYEV |
Solo X Team Project
| Name | ID |
|---|---|
| Project | PVT_kwDOCq2Q984A6EW6 |
| Status field | PVTSSF_lADOCq2Q984A6EW6zguwhjU |
| Priority field | PVTSSF_lADOCq2Q984A6EW6zguwhkA |
Status Options
| Status | Option ID |
|---|---|
| Blocked | d1cbdd71 |
| New | ce7fcfc9 |
| Backlog | f75ad846 |
| Ready | 36d4dfb8 |
| In Progress | 47fc9ee4 |
| In Review | 9ef22b4d |
| Changes Requested | 8220b383 |
| Done | 98236657 |
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 · 241 lines · 58 tokens per session scan A 238af8aa2ac1
solo-create-issue is a skill published in the GitHub repository hiero-ledger/solo (43 stars, last pushed 3d ago), licensed Apache-2.0. It adds 58 tokens to every session and 2,534 once invoked, about $0.0003 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-09-01.
Other skills, from other repositories
oss-second-contribution
Plan and execute your second and third contributions to become a regular contributor. Covers relationship building, progressive complexity escalation, and community presence. Use when your first PR was merged and you want to keep contributing, when transitioning from one-off contributor to regular, or when planning a…
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.
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.
remove
Remove a deployed framework or addon from the current workspace.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…