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/agi-comming/functional-skill-creator/createnpx skills add AGI-comming/functional-skill-creator --skill creategit clone --depth 1 https://github.com/AGI-comming/functional-skill-creatorWhat 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.00030 | $0.00281 |
| Opus 5 | $0.00015 | $0.00140 |
| Sonnet 5 | $0.00006 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
fskill-creator-create 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
fskill-creator-create
Goal
Normalize user requests for creating or enhancing functional skills into a create_context. This sub-skill only performs create/enhance pre-analysis and does not directly write target skill files.
External Inputs
| Field | Source | Description |
|---|---|---|
skill_request |
user | User-provided target skill description. |
target_skill_path |
user or repository | Directory where the functional skill should be created or updated. |
skill_name |
user or derived | Optional target skill name. |
include_viewers |
user | Whether to generate tools/log_viewer.mjs and tools/tester_viewer.mjs. |
Execution Pipeline
| Step | Function | Purpose | Input | Output |
|---|---|---|---|---|
| 1 | collect_create_brief |
Normalize user request and identify missing decisions. | skill_requesttarget_skill_pathskill_nameinclude_viewers |
create_context |
Output Scope
Only output create_context; must not directly write target skill files.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 30 lines · 30 tokens per session scan A 866fbe070f82
fskill-creator-create is a skill published in the GitHub repository AGI-comming/functional-skill-creator (359 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 281 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
LEAP
LEAP builds skills through two pipelines: Branch A distills a skill from raw data, while Branch B combines multiple skills into one. It is called by the main SkillAlchemy workflow. Use when SkillAlchemy requires distillation or fusion.
agentsop-bounded-loop
Universal discipline for any LM-driven loop — agent retries, plan-act-observe, multi-agent handoffs, optimiser passes, test-fix cycles. Encodes the one rule every framework documents quietly and every team relearns expensively: the LM in the loop is NEVER a reliable terminator. Termination must be provided by an…
agentsop-conventions-pinning
SOP for writing, loading, and evolving a project-level convention file (CONVENTIONS.md / CLAUDE.md / .cursor/rules / .clinerules / AGENTS.md) so that a coder-agent reliably respects your codebase's style choices every session. Tool-agnostic; covers the four load mechanics (read-only attachment, ancestor-walk…
agentsop-dify
SOP for building LLM applications on Dify — visual workflow + chatflow + agent + RAG knowledge base + plugin marketplace + observability, self-hostable. Use when shipping LLM apps fast with a "no-code to pro-code" gradient, especially when non-engineers need to co-author the flow.
agentsop-dspy
Operating SOP for DSPy (Stanford NLP) — the declarative framework for "programming, not prompting" language models. Activate when the user says any of: "use DSPy", "compile a prompt", "optimize prompts/programs", "MIPRO/MIPROv2", "BootstrapFewShot", "GEPA", "Signatures + Modules", "teleprompter", "auto-tune prompts…
agentsop-langgraph
Decision protocol for building, debugging, and operating LangGraph-based agent systems. Activates when a coder agent is asked to design a stateful LLM workflow, add human-in-the-loop, choose a multi-agent pattern (supervisor / swarm / hierarchical), pick a checkpoint backend, or migrate a fragile chain into a durable…