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/sync-issuenpx skills add ModelEngine-Group/fit-framework --skill sync-issuegit 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.00039 | $0.00283 |
| Opus 5 | $0.00019 | $0.00142 |
| Sonnet 5 | $0.00008 | $0.00057 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
sync-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 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
同步进度到 Issue
执行步骤
-
查找任务文件（搜索 active/blocked/completed 目录）。
-
从 task.md 中获取 issue_number、current_step、status 等。
-
读取上下文文件（analysis.md, plan.md, implementation.md, review.md），提取关键进展。
-
生成进度摘要:
## 🤖 任务进度更新 **任务ID**: <task-id> **更新时间**: <当前时间> **当前状态**: <状态描述> ### ✅ 已完成 - [x] <已完成步骤及核心要点> ### 📋 当前进展 <当前步骤详细说明> ### 🎯 下一步 <下一步计划> --- *由 Codex 自动生成* -
同步到 Issue:
gh issue comment <issue-number> --body "<摘要内容>"
注意: 摘要要简洁，面向人类阅读，建议在完成一个完整阶段后同步。
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 · 43 lines · 39 tokens per session scan A ca620b85ef20
sync-issue is a skill published in the GitHub repository ModelEngine-Group/fit-framework (2,117 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 283 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-30.
Other skills, from other repositories
reviewable-design-doc
要求・設計・アーキテクチャ・未決事項を整理し、レビュー可能な設計資料HTMLを作りたい時に使う。Use this skill to structure requirements, design, architecture, alternatives, decisions, and unresolved issues into a review-ready HTML design document. レビュー完了後はHTMLコメントを読み込み、設計へ反映し、確認が必要な場合はHTMLコメントスレッドへagent返信を書き戻す。Triggers: レビュー可能な設計資料, 設計資料をHTMLで, design doc…
review-persistence-security-resources
Normative reviewer for persistence, settings, secrets, logging hygiene, resources, caches, cross-platform behavior and long-lived state in the explyt/spring-plugin IntelliJ plugin. Use when reviewing changes that touch PersistentStateComponent, settings UI, credentials, caches, service fields, logging, file paths…
review-psi-vfs-indexing
Normative reviewer for PSI lifecycle, VFS, indexing, UAST, references, inspections, intentions and PSI performance traps in the explyt spring-plugin. Use during orchestrated code review when the diff touches PsiElement handling, VirtualFile processing, caches, indexes, completion contributors, inspections, line…
coding-guard
Compact coding guidelines for the explyt/spring-plugin repository - covers process rules (think first, simplicity, surgical changes), module layout, IntelliJ Platform threading and PSI rules, inspection and test conventions, message bundles, statistics tracking, and PR hygiene. You must call this skill before any code…
review-statistic-coverage
Usage-statistics coverage check for explyt/spring-plugin code reviews — verify that new user-visible features (quick fixes, intentions, gutter actions, completions, actions, tool-window controls, wizard steps) register usage via StatisticService and StatisticActionId. Use when reviewing a diff or PR that adds or…
github-bugs-triage
Triages the open bug queue of the explyt/spring-plugin GitHub repository: fetches the oldest open plugin-bug and compatibility issues, refines titles, suggests labels and priorities with evidence, detects duplicates, and writes a structured triage table. Use when asked to triage spring-plugin bugs, review the bug…