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 s977043/PlanGate --skill known-issues-loggit clone --depth 1 https://github.com/s977043/PlanGateWrote 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/s977043/plangate/known-issues-log)<a href="https://agentmods.dev/skills/s977043/plangate/known-issues-log"><img src="https://agentmods.dev/badge/skills/s977043/plangate/known-issues-log.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.1 | $0.00083 | $0.00449 |
| Opus 5 | $0.00042 | $0.00225 |
| Sonnet 5 | $0.00017 | $0.00090 |
| Haiku 4.5 | $0.00008 | $0.00045 |
Grade A, and why
known-issues-log 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.
What it actually says
Known Issues Log
実装過程で発生した妥協点、既知不具合、V2 候補を明文化し、handoff パッケージに統合する Skill。
カテゴリ
Review
想定 Phase
WF-05 Verify & Handoff
入力
- known-issues artifact（WF-04 出力）
- acceptance-review の出力
- 実装時に記録した TODO / FIXME コメント
出力
既知課題表:
- 既知不具合（再現手順 / 影響範囲 / 回避策）
- 妥協点（選ばなかった選択肢と理由）
- V2 候補（今回 scope 外と確認された項目、優先度付き）
- フォローアップチケット候補
使い方
- WF-05 で qa-reviewer が呼び出す
- 出力は handoff artifact に統合され、次スプリント / 別チームに引き渡される
関連
- Workflow:
docs/workflows/05_verify_and_handoff.md（配布対象外。install.sh --claude/ plugin / Codex の 3 経路とも導入先には配置されない。解決できない場合は本 Skill の記述を代替正本とし、「正本<path>を参照できなかった」と明示する） - 連携 Skill: acceptance-review
- Rule: Rule 2、Rule 5（最終成果物は毎回 handoff に集約）
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 · 43 lines · 83 tokens per session scan A ae933badd939
known-issues-log is a skill published in the GitHub repository s977043/PlanGate (2 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 449 once invoked, about $0.0004 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
skill-maintenance
Automated skill maintenance tool (v6 — Unified Registry + Snapshots). Full scan: [Orphan] migrate misplaced skills from category dirs OR standalone skills/<name>/ to auto-generated/, [Sync] auto-generated/ vs registry lifecycle diff (new/deleted/revived + description auto-sync via lifecycle field), [Reg]…
extract
Run the full Semantica semantic extraction pipeline on a file or selected text — NER, relations, events, coreference resolution, triplets, and validation. Clears result cache before each run. Returns Markdown tables with entity/relation/event/triplet results and inline validator warnings.
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.