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/workergit 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/worker)<a href="https://agentmods.dev/commands/flagler-county-bocc/mcp-forge/worker"><img src="https://agentmods.dev/badge/commands/flagler-county-bocc/mcp-forge/worker.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.00608 |
| Opus 5 | $0.00000 | $0.00304 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
worker 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Entrypoint — worker
This file is consumed by Step 8 of the rewrite process. Apply when
AUDIT_MANIFEST.projectType === "worker".
src/worker.ts — Process Entry
import { config } from './config/index.js';
import { logger } from './lib/logger.js';
import { startScheduler, stopScheduler } from './scheduler.js';
async function main(): Promise<void> {
logger.info({ env: config.env }, 'Worker starting');
await startScheduler();
logger.info('Worker ready — consuming jobs');
}
async function shutdown(signal: string): Promise<void> {
logger.info({ signal }, 'Shutting down worker');
await stopScheduler();
process.exit(0);
}
process.on('SIGTERM', () => void shutdown('SIGTERM'));
process.on('SIGINT', () => void shutdown('SIGINT'));
process.on('unhandledRejection', (reason) => {
logger.fatal({ reason }, 'Unhandled promise rejection');
process.exit(1);
});
void main();
src/scheduler.ts — Job Registration
export async function startScheduler(): Promise<void> {
// Register each job from AUDIT_MANIFEST job handlers
// e.g. queue.process('<job-name>', concurrency, <job-name>Handler);
}
export async function stopScheduler(): Promise<void> {
// Gracefully close queue connections
}
src/jobs//.handler.ts
import { validate } from '../../lib/validate.js';
import { <JobName>PayloadSchema } from './<job-name>.schema.js';
import { <jobName>Service } from '../../lib/container.js';
import { createLogger } from '../../lib/logger.js';
const log = createLogger({ module: '<job-name>Handler' });
export async function <jobName>Handler(job: Job): Promise<void> {
const payload = validate(<JobName>PayloadSchema, job.data);
log.info({ jobId: job.id }, '<job-name> started');
await <jobName>Service.<method>(payload);
log.info({ jobId: job.id }, '<job-name> completed');
}
Rules:
- Every handler validates its payload with
validate()before processing. - Handlers must be idempotent — running the same job twice must not cause double side-effects.
- Log job start and completion with
jobIdin context. - Handlers throw
AppErrorsubclasses on business failures; the queue library handles retries. - Never call
process.exit()inside a handler.
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.
- 3d ago First seen · 76 lines · 0 tokens per session scan A 5fb009a11029
worker 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 608 tokens. 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.