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/stumason/coolify-mcp/smoke-testgit clone --depth 1 https://github.com/StuMason/coolify-mcpWrote 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/stumason/coolify-mcp/smoke-test)<a href="https://agentmods.dev/commands/stumason/coolify-mcp/smoke-test"><img src="https://agentmods.dev/badge/commands/stumason/coolify-mcp/smoke-test.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.1 | $0.00011 | $0.00541 |
| Opus 5 | $0.00005 | $0.00270 |
| Sonnet 5 | $0.00002 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
smoke-test 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 6d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smoke Test
Build the project and run integration smoke tests against the live Coolify instance to verify fixes work end-to-end.
Workflow
1. Build
npm run build
If build fails, stop and report the error.
2. Run integration tests
npm run test:integration -- --testPathPattern=smoke
Report which tests passed and failed.
3. Quick manual checks (optional)
If an argument is provided (e.g. /smoke-test version), run targeted checks:
version
Verify the VERSION export matches package.json:
node --input-type=module -e "import { VERSION } from './dist/lib/mcp-server.js'; import { createRequire } from 'module'; const r = createRequire(import.meta.url); const pkg = r('./package.json'); console.log('MCP VERSION:', VERSION, VERSION === pkg.version ? 'OK' : 'MISMATCH (expected ' + pkg.version + ')');"
errors
Trigger a validation error against the live API to confirm error handling works:
node --input-type=module -e "
import { config } from 'dotenv'; config();
import { CoolifyClient } from './dist/lib/coolify-client.js';
const client = new CoolifyClient({ baseUrl: process.env.COOLIFY_URL, accessToken: process.env.COOLIFY_TOKEN });
const servers = await client.listServers();
try {
await client.createService({ server_uuid: servers[0].uuid, project_uuid: 'nonexistent', environment_name: 'production', docker_compose_raw: 'services:\n test:\n image: nginx' });
} catch (e) { console.log('Error handled:', e.message); }
"
connect
Just verify API connectivity:
node --input-type=module -e "
import { config } from 'dotenv'; config();
import { CoolifyClient } from './dist/lib/coolify-client.js';
const client = new CoolifyClient({ baseUrl: process.env.COOLIFY_URL, accessToken: process.env.COOLIFY_TOKEN });
const v = await client.getVersion(); console.log('Coolify API:', v);
const servers = await client.listServers(); console.log('Servers:', servers.length);
"
4. Report
Summarize results concisely: what passed, what failed, any issues found.
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.
- 6d ago First seen · 73 lines · 11 tokens per session scan A 8f61995191be
smoke-test is a command published in the GitHub repository StuMason/coolify-mcp (578 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 541 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-08-30.
Other commands, from other repositories
validate-dependencies
Validate all task dependencies for issues.
domain-research
Conduct domain research covering industry analysis, regulations, technology trends, and ecosystem dynamics using current web data and verified sources.
validate-prd
Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality.
editorial-review-structure
Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension.
add-tool
Scaffold a new FreeAgent MCP tool (handler + registration + test) following the repo pattern.
compile
Compile a FIBER decision context (world + query) and report the oracle verdict, omission accounting, and certificate digest faithfully.