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 commands/flagler-county-bocc/mcp-forge/mcp-servergit clone --depth 1 https://github.com/Flagler-County-BoCC/mcp-forgeWrote 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/commands/flagler-county-bocc/mcp-forge/mcp-server)<a href="https://agentmods.dev/commands/flagler-county-bocc/mcp-forge/mcp-server"><img src="https://agentmods.dev/badge/commands/flagler-county-bocc/mcp-forge/mcp-server.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.00000 | $0.06963 |
| Opus 5 | $0.00000 | $0.03481 |
| Sonnet 5 | $0.00000 | $0.01393 |
| Haiku 4.5 | $0.00000 | $0.00696 |
Grade B, and why
mcp-server scanned grade B with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
// ~/.claude.json — NOT ~/.claude/settings.json (that file is for preferences, not MCP) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const client = axios.create({ How it starts
The opening of the file, as written. The whole thing — 712 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Entrypoint — mcp-server
This file is consumed by Step 8 of the rewrite process. Apply when
AUDIT_MANIFEST.projectType === "mcp-server".
Architecture Overview
src/stdio.ts ← process entry; connects StdioServerTransport; never imported by tests
src/server.ts ← McpServer factory; registers all tools; importable with no side effects
src/tools/<module>/ ← one folder per logical tool group (module)
src/lib/
container.ts ← wires HTTP client → services; exports service instances
http-client.ts ← axios/got client with auth interceptors + error normalization
src/config/ ← zod-validated env (from Step 2)
src/errors/ ← AppError hierarchy (from Step 4)
src/server.ts — McpServer Factory
import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
import { config } from './config/index.js';
import { register<Module>Tools } from './tools/<module>/<module>.tool.js';
// one import per module in AUDIT_MANIFEST.mcpTools[*].module (deduplicated)
export function createServer(): McpServer {
const server = new McpServer({
name: config.app?.name ?? '<projectName>',
version: process.env['npm_package_version'] ?? '0.0.0',
});
// Register tools in alphabetical module order
register<Module>Tools(server);
// ...
return server;
}
server.ts must NOT call server.connect() — that is stdio.ts's job. This makes server.ts testable without side effects.
src/stdio.ts — Process Entry
import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
import { createServer } from './server.js';
import { logger } from './lib/logger.js';
import { config } from './config/index.js';
async function main(): Promise<void> {
const server = createServer();
const transport = new StdioServerTransport();
await server.connect(transport);
logger.info(
{
app: config.app?.name ?? 'mcp-server',
env: config.env,
profile: config.mcp?.activeProfile ?? 'default',
},
'MCP stdio server started',
);
}
process.on('SIGTERM', () => {
logger.info('SIGTERM received — shutting down');
process.exit(0);
});
process.on('SIGINT', () => {
logger.info('SIGINT received — shutting down');
process.exit(0);
});
process.on('unhandledRejection', (reason) => {
logger.fatal({ reason }, 'Unhandled promise rejection');
process.exit(1);
});
void main().catch((err) => {
logger.fatal({ err }, 'Failed to start MCP server');
process.exit(1);
});
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 · 712 lines · 0 tokens per session scan B d5ad609db3ba
mcp-server is a command published in the GitHub repository Flagler-County-BoCC/mcp-forge (1 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,963 tokens. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.