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/modelengine-group/fit-framework/analyze-codescannpx skills add ModelEngine-Group/fit-framework --skill analyze-codescangit clone --depth 1 https://github.com/ModelEngine-Group/fit-frameworkWhat 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.00053 | $0.00321 |
| Opus 5 | $0.00026 | $0.00161 |
| Sonnet 5 | $0.00011 | $0.00064 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
analyze-codescan 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 2d 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.
What it actually says
分析 Code Scanning 告警
分析指定的 Code Scanning（CodeQL）告警，评估安全风险并创建修复任务。
执行步骤
-
获取告警信息:
gh api repos/{owner}/{repo}/code-scanning/alerts/<alert-number>提取: rule (id/severity/description), tool (name), most_recent_instance (location/message)
-
创建任务目录和文件，基于 .agents/templates/task.md 模板。
-
定位和分析源码:
- 根据 most_recent_instance.location 定位源码文件和行号
- 读取告警所在的源码上下文
- 理解 CodeQL 规则的含义和检测逻辑
- 检查是否有其他位置也存在相同问题
-
评估安全风险（代码路径可达性、可利用性、影响程度）。
-
输出分析文档到 analysis.md。
-
更新任务状态。
-
提示下一步: plan-task 设计修复方案，或 close-codescan 关闭告警。
注意: Critical/High 级别立即处理，Medium 计划处理，Low 可延后。
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.
- 2d ago First seen · 35 lines · 53 tokens per session scan A 154d1c3b8e73
analyze-codescan is a skill published in the GitHub repository ModelEngine-Group/fit-framework (2,117 stars, last pushed 5mo ago), licensed MIT. It adds 53 tokens to every session and 321 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-08-30.
Other skills, from other repositories
mechanical-engineering-research
Apply source-aware mechanical-engineering judgment to research, analysis, coding, writing, teaching, research identity, and release work. Use for thermal-fluid systems, heat transfer, fluid mechanics, thermodynamics, HVAC, energy systems, turbomachinery, piping, multiphase flow, experiments, correlations, CFD…
swarm
Launching multi-agent parallel work with the Agentic SDLC. Use when a task benefits from decomposition into parallel subtasks.
finish
Completing a development branch for merge readiness. Use when implementation and tests pass and the branch needs formal preparation for review and merge.
grill
Interrogating requirements to validate before building. Use before swarm decomposition, design decisions on ambiguous features, or when scope creep risk is high.
team
Referencing the agent roster, roles, coordination model, and dispatch modes. Use when spawning agents or checking permissions.
ticket
Associate every PDS task with a GitHub issue. Orchestrator finds or creates the ticket, posts plan and acceptance criteria as a checkbox list, updates it as work progresses. Use at Phase 1 of every swarm.