A workflow that prepares an issue for implementation by creating a summary, complexity assessment, ordered tasks, related references, and a Claude Code prompt.

Use it to inspect issue scope, find related issues and notes, identify affected technical layers, and produce implementation guidance.

It turns a loosely described issue into a clearer plan that a developer or coding agent can follow.

ai-context — Skill for Claude Code and Codex by pilotspace/pilot-space

Install

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.

Any agent

npx skills add pilotspace/pilot-space --skill ai-context

Clone the repo

git clone --depth 1 https://github.com/pilotspace/pilot-space

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pilotspace/pilot-space/ai-context/github.svg)](https://agentmods.dev/skills/pilotspace/pilot-space/ai-context)

Your own site

<a href="https://agentmods.dev/skills/pilotspace/pilot-space/ai-context"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/ai-context/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/pilotspace/pilot-space/ai-context"><img src="https://agentmods.dev/badge/skills/pilotspace/pilot-space/ai-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,998 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00017	$0.01998
Opus 5.5	$0.00007	$0.00799
Sonnet 5.5	$0.00003	$0.00400
Haiku 4.5	$0.00002	$0.00200

Measured 2mo ago against content hash 0c111983f783, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ai-context 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.

backend/src/pilot_space/ai/templates/skills/ai-context/SKILL.md · 251 lines

How it starts

The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AI Context Skill

Generate comprehensive developer context for an issue: summary, complexity analysis, implementation tasks, related content, and a ready-to-use Claude Code prompt.

Quick Start

Use this skill when:

Developer opens "AI Context" tab on an issue detail page
User explicitly requests context generation (/ai-context)
System needs structured implementation guidance for an issue

Example:

Issue: "PILOT-42: Implement real-time notifications"

AI generates:
- Summary: Architecture overview + scope analysis
- Complexity: high (cross-cutting: backend + frontend + infra)
- Tasks: 6 ordered subtasks with estimates and dependencies
- Claude Code Prompt: Ready-to-use implementation guide

Workflow

Analyze the Issue
- Read the issue title, description, and metadata
- Understand scope, complexity, and technical requirements
- Identify the technical layers involved (DB, API, Frontend, Tests)
Identify Related Content
- Use search_issues to find related or similar issues in the workspace
- Use search_notes to find relevant notes and documentation
- Check for linked PRs, commits, and code references
Assess Complexity
- low: Single layer, straightforward implementation, 1-2 files
- medium: Multiple files, standard patterns, some cross-cutting
- high: Cross-layer changes, new architecture, significant testing
Generate Implementation Tasks
- Break down into ordered, actionable subtasks
- Identify dependencies between tasks (DAG structure)
- Estimate effort per task: S (~1h), M (~2-3h), L (~4-6h), XL (~8h+)
- Follow decomposition patterns:
  - Backend: DB schema → Repository → Service → API → Tests
  - Frontend: Component → State → Styling → Tests
  - Full-stack: Backend → Frontend → Integration tests
Create Claude Code Prompt
- Summarize context for AI-assisted development
- List relevant code files and references
- Include implementation instructions and constraints
- Reference existing patterns and conventions

Read the full file on GitHub · 251 lines

Changes

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 · 251 lines · 17 tokens per session scan A 0c111983f783

Subscribe to this mod's changes

ai-context is a skill published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,998 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.

Planning

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens