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 konglong87/methodology-skills --skill pilotgit clone --depth 1 https://github.com/konglong87/methodology-skillsWrote 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/konglong87/methodology-skills/pilot)<a href="https://agentmods.dev/skills/konglong87/methodology-skills/pilot"><img src="https://agentmods.dev/badge/skills/konglong87/methodology-skills/pilot/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/konglong87/methodology-skills/pilot"><img src="https://agentmods.dev/badge/skills/konglong87/methodology-skills/pilot.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.00047 | $0.03552 |
| Opus 5 | $0.00023 | $0.01776 |
| Sonnet 5 | $0.00009 | $0.00710 |
| Haiku 4.5 | $0.00005 | $0.00355 |
Grade A, and why
pilot 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 8d 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 — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pilot - 技能领航员
前置协议
环境检测
PROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo "unknown")
BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
COMMIT=$(git rev-parse --short HEAD 2>/dev/null || echo "unknown")
echo "PROJECT: $PROJECT_ROOT"
echo "BRANCH: $BRANCH"
echo "COMMIT: $COMMIT"
工件目录初始化
mkdir -p memory/artifacts/pilot
经验读取(推荐)
触发时机:分析任务类型前,为当前任务准备最佳实践
推荐动作:调用 experience-manager 技能检索相关经验
执行步骤:
-
提取任务关键词
从用户请求中提取: - 核心任务关键词 - 技术栈关键词 - 问题类型关键词 -
写入请求工件
Write( file_path="memory/artifacts/pilot/experience-request.json", content={ "requesting_skill": "pilot", "action": "retrieve", "task_keywords": ["关键词1", "关键词2"], "task_type": "bugfix|feature|refactor", "technologies": ["Technology1", "Technology2"] } ) -
读取经验结果
result = Read("memory/artifacts/experience-manager/experience-result.json") -
应用到技能推荐
基于历史经验,推荐以下技能链: 1. /investigate - 快速定位问题(历史成功率 90%) 2. /first-principles - 分析根本原因(历史应用 5 次) 3. /pdca-cycle - 迭代优化 ⚠️ 预防措施(来自历史经验): - 新项目优先检查国际化配置 - 使用标准配置模板
价值:基于历史经验优化技能推荐,提高成功率。
错误预防(自动)
触发时机:检测到潜在错误风险时
自动动作:调用 experience-manager 获取预防建议
执行步骤:
-
检测风险
在分析任务类型时,检测常见的错误风险: - 缺少配置检查 - 使用了已废弃的API - 忽略了边界情况 -
写入预防请求
Write( file_path="memory/artifacts/pilot/error-prevention-request.json", content={ "requesting_skill": "pilot", "action": "prevent", "current_step": "任务分析", "context": { "technology": "...", "feature": "...", "risk_factors": [...] } } ) -
展示预防建议
## 💡 错误预防提醒 检测到潜在风险:国际化配置缺失 **预防措施**: - 优先检查 next.config.js 中的 i18n 配置 - 使用标准配置模板 **历史错误**:2026-03-20 类似错误
价值:提前预防错误,避免重复踩坑。
Overview
智能分析用户请求,推荐最佳的方法论技能组合,实现技能协同工作。
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.
- 8d ago First seen · 550 lines · 47 tokens per session scan A a6eede752247
pilot is a skill published in the GitHub repository konglong87/methodology-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 3,552 once invoked, about $0.0002 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
importing-a-codebase
Use when the repo holds real source code but no specs: the existing-codebase branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for empty workspaces (starting-a-new-project) or feature work in a specced project (brainstorming).
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
brainstorming
Use this BEFORE any creative or feature work: building a new feature, adding functionality, changing behavior, or making a nontrivial design decision. Turns the user's request into a validated design — recorded as a spec-graph task-spec — before any implementation. Do not skip this because a change looks small.
reviewing-changes
Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with addreviewcomment, and settle with exactly one reviewverdict.