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/directory-basednpx skills add agentfront/frontmcp --skill directory-basedgit 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/directory-based)<a href="https://agentmods.dev/skills/agentfront/frontmcp/directory-based"><img src="https://agentmods.dev/badge/skills/agentfront/frontmcp/directory-based.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.00028 | $0.00878 |
| Opus 5 | $0.00014 | $0.00439 |
| Sonnet 5 | $0.00006 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
directory-based-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 today.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directory-Based Skill with File References and Registration
A skill loaded from a directory structure with SKILL.md frontmatter, plus file-based and URL-based instruction sources.
Code
skills/
coding-standards/
SKILL.md # Instructions with YAML frontmatter
scripts/
lint-check.sh # Helper scripts referenced in instructions
references/
patterns.md # Reference documentation appended to context
assets/
diagram.png # Visual assets
## <!-- skills/coding-standards/SKILL.md -->
name: coding-standards
description: Project coding standards and patterns
tags: [standards, conventions, quality]
parameters:
- name: language
description: Target programming language
type: string
default: typescript
examples:
- scenario: Apply coding standards to a new module
expected-outcome: Code follows all project conventions
---
# Coding Standards
Follow these standards when writing code for this project...
// src/skills/load-skills.ts
import { skillDir, skill } from '@frontmcp/sdk';
// Load a directory-based skill with bundled scripts, references, and assets
const CodingStandards = await skillDir('./skills/coding-standards');
// File-based instructions -- path resolves relative to this file's directory
const DeployGuide = skill({
name: 'deploy-guide',
description: 'Step-by-step deployment checklist',
instructions: { file: './docs/deploy-guide.md' }, // resolves to src/skills/docs/deploy-guide.md
});
// src/server.ts
import { FrontMcp, App, Skill, SkillContext } from '@frontmcp/sdk';
// URL-based instructions fetched at build time
@Skill({
name: 'api-standards',
description: 'REST API design standards',
instructions: { url: 'https://docs.example.com/standards/api-design.md' },
})
class ApiStandardsSkill extends SkillContext {}
// ESM and remote loading
const ExternalGuide = Skill.esm('@my-org/skills@^1.0.0', 'ExternalGuide', {
description: 'A skill loaded from an ES module',
});
const CloudGuide = Skill.remote('https://example.com/skills/style-guide', 'CloudGuide', {
description: 'A skill loaded from a remote server',
});
@App({
name: 'standards-app',
skills: [CodingStandards, DeployGuide, ApiStandardsSkill, ExternalGuide, CloudGuide],
})
class StandardsApp {}
@FrontMcp({
info: { name: 'dev-server', version: '1.0.0' },
apps: [StandardsApp],
})
class DevServer {}
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.
- today First seen · 116 lines · 28 tokens per session scan A 81e17c66eecc
directory-based-skill is a skill published in the GitHub repository agentfront/frontmcp (146 stars, last pushed 2d ago), licensed Apache-2.0. It adds 28 tokens to every session and 878 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
axiom-sre
Expert SRE investigator for incidents and debugging. Uses hypothesis-driven methodology and systematic triage. Can query Axiom observability when available. Use for incident response, root cause analysis, production debugging, or log investigation.
building-dashboards
Designs and builds Axiom dashboards via API. Covers chart types, APL and metrics/MPL query patterns, SmartFilters, layout, and configuration options. Use when creating dashboards, migrating from Splunk, or configuring chart options.
axiom-alerting
Create and manage Axiom monitors and notifiers via the v2 public API. Use when building alerting, routing notifications, validating monitor behavior, and maintaining alert configurations end-to-end.
clawhub-moderation
Use for ClawHub staff moderation actions with the repo-local ClawHub admin tool: skills, users, org publishers, plugin packages, trusted publishers, official publishers, and guarded staff email.
clawhub-pr-maintainer
Use when reviewing, triaging, validating, or discussing ClawHub GitHub issues or pull requests, including author context, CI, UI proof, evidence, labels, close decisions, and maintainer handoff.