Borrowing it
Nothing to install: this file belongs to akaghef/M3E. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/akaghef/M3E/main/.claude/skills/pj04-template-system/SKILL.mdgit clone --depth 1 https://github.com/akaghef/M3EWrote 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/akaghef/m3e/pj04-template-system)<a href="https://agentmods.dev/skills/akaghef/m3e/pj04-template-system"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/pj04-template-system/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/akaghef/m3e/pj04-template-system"><img src="https://agentmods.dev/badge/skills/akaghef/m3e/pj04-template-system.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.00175 | $0.01860 |
| Opus 5.5 | $0.00070 | $0.00744 |
| Sonnet 5.5 | $0.00035 | $0.00372 |
| Haiku 4.5 | $0.00017 | $0.00186 |
Grade A, and why
pj04-template-system 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 5d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PJ04 Template System
このスキルは、PJ04 の Template System Spec -> AppState -> GraphSpec -> local run -> trace/artifact の CLI ループを Claude が安全に使うための操作手順。
Product Context
PJ04 の目的は M3E を LangGraph 系システムの協働 authoring 環境 にすること。 M3E では system を直接コードで書かず、Map / Template System Spec から実行契約を作る。
標準ループ:
System Block Template catalog
-> Template System Spec (YAML/JSON)
-> AppState
-> GraphSpec
-> local run
-> trace / artifact
Source Of Truth
| 目的 | ファイル |
|---|---|
| PJ04全体戦略 | projects/PJ04_MermaidSystemLangGraph/docs/global_strategy.md |
| Template仕様 | projects/PJ04_MermaidSystemLangGraph/docs/system_block_templates.md |
| LangGraph到達度 | projects/PJ04_MermaidSystemLangGraph/docs/langgraph_feature_coverage.md |
| PJv34 spec | projects/PJ04_MermaidSystemLangGraph/templates/pjv34_weekly_review.yaml |
| PJv* factory package | projects/PJ04_MermaidSystemLangGraph/instructions/pjv_factory/README.md |
| PJv* Master指示 | projects/PJ04_MermaidSystemLangGraph/instructions/pjv_factory/master_instruction.md |
| PJv* batch queue | projects/PJ04_MermaidSystemLangGraph/instructions/pjv_factory/batch_manifest.yaml |
| Template型 | beta/src/shared/template_system_spec.ts |
| Builder | beta/src/node/template_system_builder.ts |
| Build CLI | beta/src/node/template_build_cli.ts |
| Run CLI | beta/src/node/template_run_cli.ts |
| Tests | beta/tests/unit/template_system_builder.test.js |
Current PJv34 Status
PJv34 Weekly Review はすでに Template System Spec としてテンプレ化済み。
実体:
projects/PJ04_MermaidSystemLangGraph/templates/pjv34_weekly_review.yaml
上位 system:
Load Context -> Generate Doc -> Write Output
Generate Doc subsystem 内部:
Build Prompt
-> Call Provider
-> Evaluate Response
-> pass: Return Draft
-> api_error: Retry / Backoff -> retry: Call Provider / exhausted: Fallback / Qn
-> bad_output: Fallback / Qn
Commands
すべて repo root ではなく beta/ で実行する。
Build
YAML/JSON spec から AppState / GraphSpec / warnings / validation を出す。
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.
- 5d ago First seen · 196 lines · 175 tokens per session scan A 00efd9ba9345
pj04-template-system is a skill published in the GitHub repository akaghef/M3E (11 stars, last pushed 5d ago), licensed MIT. It adds 175 tokens to every session and 1,860 once invoked, about $0.0007 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-10-02.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…