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/pilotspace/pilot-space/enhance-issuenpx 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.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 | $0.00020 | $0.01559 |
| Opus 5 | $0.00010 | $0.00779 |
| Sonnet 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 4d 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.
- 4d 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 2mo 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. 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
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
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…
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
project-init
Scaffold an unconfigured directory into a configured pi project. Interactive, profile-driven: previews the planned writes, then writes AGENTS.md, .pi/settings.json and prompt files — optionally also a knowledge base, an openspec/ scaffold, and user-global /.pi/agent/settings.json. Use on a bare directory, or when the…