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/agentfront/frontmcp/createnpx skills add agentfront/frontmcp --skill creategit clone --depth 1 https://github.com/agentfront/frontmcpWrote 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/agentfront/frontmcp/create)<a href="https://agentmods.dev/skills/agentfront/frontmcp/create"><img src="https://agentmods.dev/badge/skills/agentfront/frontmcp/create.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 | $0.00017 | $0.05745 |
| Opus 5 | $0.00009 | $0.02873 |
| Sonnet 5 | $0.00003 | $0.01149 |
| Haiku 4.5 | $0.00002 | $0.00575 |
Grade A, and why
create-skill 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 yesterday.
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 — 668 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Instruction-Only Skills
Skills are knowledge and workflow packages that teach AI clients how to accomplish tasks. Unlike tools (which execute actions) or agents (which run autonomous LLM loops), a skill provides structured instructions that the AI follows on its own. An instruction-only skill contains no tool references -- it is purely a guide.
When to Use This Skill
Must Use
- You need to package knowledge, conventions, or workflow steps as a reusable skill that AI clients can follow
- You are creating a SKILL.md catalog entry or a class/function-based skill with no tool dependencies
- You want to enforce coding standards, onboarding steps, or review criteria through structured AI guidance
Recommended
- You are building a deployment runbook, architecture decision record, or quality gate checklist
- You want to share workflow templates across teams via MCP or HTTP discovery endpoints
- You need parameterized instructions that callers can customize per invocation
Skip When
- The skill must invoke MCP tools during execution -- use
create-skill-with-toolsinstead - You need an autonomous agent loop rather than static instructions -- use an agent pattern instead
- The content is a one-off prompt with no reuse value -- a plain prompt template is simpler
Decision: Pick this skill when you need a reusable, instruction-only knowledge package that guides AI through a workflow without requiring tool calls.
Class-Based Pattern
Create a class extending SkillContext and decorate it with @Skill. The decorator requires name, description, and instructions.
SkillMetadata Fields
| Field | Type | Required | Description |
|---|---|---|---|
name |
string |
Yes | Unique skill name in kebab-case (max 64 chars) |
description |
string |
Yes | Short description (max 1024 chars, no HTML/XML) |
instructions |
string | { file: string } | { url: string } |
Yes | The skill content -- see instruction sources below |
parameters |
SkillParameter[] |
No | Customization parameters for the skill |
examples |
SkillExample[] |
No | Usage scenarios and expected outcomes |
tags |
string[] |
No | Categorization tags for discovery |
visibility |
'mcp' | 'http' | 'both' |
No | Where the skill is discoverable (default: 'both') |
hideFromDiscovery |
boolean |
No | Register but hide from listing endpoints (default: false) |
priority |
number |
No | Search ranking weight; higher = earlier (default: 0) |
toolValidation |
'strict' | 'warn' | 'ignore' |
No | Behavior when referenced tools are missing (default: 'warn') |
license |
string |
No | License identifier per Agent Skills spec (e.g., 'MIT') |
compatibility |
string |
No | Environment requirements (max 500 chars) |
specMetadata |
Record<string, string> |
No | Arbitrary key-value map (Agent Skills spec metadata field) |
allowedTools |
string |
No | Space-delimited pre-approved tool names (Agent Skills spec) |
resources |
SkillResources |
No | Bundled dirs: { scripts?, references?, assets? } |
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.
- yesterday First seen · 668 lines · 17 tokens per session scan A 9f04e69abe41
create-skill is a skill published in the GitHub repository agentfront/frontmcp (146 stars, last pushed 3d ago), licensed Apache-2.0. It adds 17 tokens to every session and 5,745 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
reference-compiler-cli
Explains the mental model and architecture of the code under packages/compiler-cli. You MUST use this skill any time you plan to work with code in packages/compiler-cli.
reference-core
Explains the mental model and architecture of the code under packages/core. You MUST use this skill any time you plan to work with code in packages/core.
playwright
Use when the task requires capturing or automating a real browser from the terminal.
write-concept
Write or review JavaScript concept documentation pages for the 33 JavaScript Concepts project, following strict structure and quality guidelines.
concept-workflow
End-to-end workflow for creating complete JavaScript concept documentation, orchestrating all skills from research to final review.
fact-check
Verify technical accuracy of JavaScript concept pages by checking code examples, MDN/ECMAScript compliance, and external resources to prevent misinformation.