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/petrowsky/agentic-fm/implementation-plannpx skills add petrowsky/agentic-fm --skill implementation-plangit clone --depth 1 https://github.com/petrowsky/agentic-fmWhat 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.00068 | $0.01090 |
| Opus 5 | $0.00034 | $0.00545 |
| Sonnet 5 | $0.00014 | $0.00218 |
| Haiku 4.5 | $0.00007 | $0.00109 |
Grade A, and why
implementation-plan 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 127 lines · 68 tokens per session scan A 2c9a037e4b50
implementation-plan is a skill published in the GitHub repository petrowsky/agentic-fm (92 stars, last pushed 18d ago), with no licence file. It adds 68 tokens to every session and 1,090 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
filemaker-layout-xml
Use this skill whenever the user wants to work with FileMaker layout XML. This includes generating paste-ready layout object XML (fmxmlsnippet type LayoutObjectList) from descriptions, reviewing layout XML for silent paste-handler failures, or analysing Save as XML layout exports. Trigger any time the user mentions…
claris-filemaker-pro
REFERENCE skill — FileMaker Pro script steps, calculation functions, and field types. Use for: syntax lookups, function parameters and return types, per-step platform support across FileMaker Pro, Go, WebDirect, Server, Cloud, Data API and Custom Web Publishing, field type capabilities, usage examples, and live doc…
filemaker-field-xml
Use this skill whenever the user wants to work with FileMaker schema definition XML — field definitions, table definitions, or value list definitions. This includes generating paste-ready field definitions (fmxmlsnippet type FMObjectList containing Field elements) for the Fields tab, complete tables (BaseTable…
filemaker-ai-vocabulary
Use this skill whenever Claude needs to name, call, or validate a FileMaker function or script step — writing a calculation, writing a script, checking whether a function or script step exists, checking parameter order or count, or checking whether a script step is supported on a given platform (Pro, Go, WebDirect…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
omh-code-review
This is a Hermes-native code-review workflow skill.