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 pilotspace/pilot-space --skill enhance-issuegit clone --depth 1 https://github.com/pilotspace/pilot-spaceWrote 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/pilotspace/pilot-space/enhance-issue)<a href="https://agentmods.dev/skills/pilotspace/pilot-space/enhance-issue"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/enhance-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/pilotspace/pilot-space/enhance-issue"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/enhance-issue.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.01559 |
| Opus 5.5 | $0.00008 | $0.00624 |
| Sonnet 5.5 | $0.00004 | $0.00312 |
| Haiku 4.5 | $0.00002 | $0.00156 |
Grade A, and why
enhance-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 2mo 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enhance Issue Skill
Automatically enhance issue metadata using AI analysis of title and description.
Quick Start
Use this skill when:
- User creates minimal issue (only title)
- Issue lacks labels, priority, or acceptance criteria
- User requests AI enhancement (
/enhance-issue)
Example:
User creates issue:
Title: "Login not working"
AI enhances:
- Labels: ["bug", "backend", "authentication", "critical"]
- Priority: "critical" (blocks user access)
- Acceptance Criteria:
- [ ] Users can log in with valid credentials
- [ ] Error messages are clear for invalid credentials
- [ ] Session persists after login
Workflow
-
Analyze Issue Context
- Parse title for keywords (fix, implement, bug, feature)
- Analyze description for technical details
- Check for urgency markers (critical, urgent, blocking)
- Identify domain from keywords (auth, api, ui, db)
-
Suggest Labels
- Type: bug, feature, enhancement, documentation, chore
- Domain: backend, frontend, infrastructure, security
- Technology: python, typescript, react, postgresql
- Status: needs-investigation, blocked, ready
- Use RECOMMENDED for clear matches, DEFAULT for inferred
-
Infer Priority
- Critical: Security vulnerabilities, data loss, complete feature breakage
- High: Major functionality broken, significant user impact
- Medium: Partial functionality affected, workarounds exist
- Low: Minor issues, cosmetic improvements, nice-to-have features
-
Generate Acceptance Criteria
- Extract implied requirements from description
- Add standard criteria based on issue type:
- Bugs: Reproduction steps, expected behavior, error handling
- Features: Happy path, edge cases, error states
- Format as checklist for task tracking
Output Format
{
"suggested_labels": [
{"label": "bug", "confidence": "RECOMMENDED", "rationale": "Title contains 'not working'"},
{"label": "backend", "confidence": "RECOMMENDED", "rationale": "Login is server-side functionality"},
{"label": "authentication", "confidence": "RECOMMENDED", "rationale": "Login relates to auth"},
{"label": "critical", "confidence": "RECOMMENDED", "rationale": "Blocks user access"}
],
"suggested_priority": {
"priority": "critical",
"confidence": "RECOMMENDED",
"rationale": "Complete feature breakage preventing user access"
},
"acceptance_criteria": [
{"text": "Users can log in with valid email and password", "confidence": "RECOMMENDED"},
{"text": "Error messages are displayed for invalid credentials", "confidence": "RECOMMENDED"},
{"text": "Session persists after successful login", "confidence": "DEFAULT"},
{"text": "Login form validates input client-side", "confidence": "DEFAULT"}
],
"estimated_complexity": {
"level": "medium",
"confidence": "DEFAULT",
"rationale": "Likely requires debugging auth flow, not full reimplementation"
}
}
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.
- 2mo ago First seen · 201 lines · 20 tokens per session scan A e665f60e22ce
enhance-issue is a skill published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 1,559 once invoked, about $0.0001 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-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…