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 skills add me-cedric/agent-compass --skill local-rungit clone --depth 1 https://github.com/me-cedric/agent-compassWrote 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/me-cedric/agent-compass/local-run)<a href="https://agentmods.dev/skills/me-cedric/agent-compass/local-run"><img src="https://agentmods.dev/badge/skills/me-cedric/agent-compass/local-run/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/me-cedric/agent-compass/local-run"><img src="https://agentmods.dev/badge/skills/me-cedric/agent-compass/local-run.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.01040 |
| Opus 5.5 | $0.00013 | $0.00416 |
| Sonnet 5.5 | $0.00007 | $0.00208 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
local-run 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 10d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
local-run
Run the local stack with ac dev. One file, process-compose.yaml, lists every process.
Never start process-compose directly. ac dev sets the socket path and the timeouts.
1. Ask before you write
Ask for each input that the repository does not show. Ask one question at a time. Do not guess.
- Secrets: use the
envskill andac env importto get the values. Never ask the user to paste a secret in chat. - VPN: does an app or a registry need it? Is it on?
- Corporate certificates: when Node fails with a certificate error, set
NODE_EXTRA_CA_CERTSto the CA file. Or setNODE_OPTIONS=--use-system-ca. - Docker: is the daemon running? Check with
docker info. Dockerfiles and a compose file to adapt are indocs/agent-compass/packs/local-run/extras/. Sync does not install them. - Mobile: which target? iOS needs Xcode and a simulator. Android needs the SDK and an emulator.
- Apps: which apps must run now? Which ports are already in use?
2. Start from a draft
ac dev up --dry
When process-compose.yaml is missing, this prints a draft on stdout. It writes nothing.
The draft has one infra process for the first compose file. It has one process for each app with a dev script.
When the file exists, the same command validates it.
Read the warnings. A missing port means the process has no readiness probe. Two apps on one port is a clash.
Save the draft as process-compose.yaml. Then edit it.
3. Write the file
For each app process:
- Add a
readiness_probeon the app port. The draft usesnc -z 127.0.0.1 <port>. - Add a
log_locationof.agents/dev/logs/<name>.log. - Set
working_dirrelative to the repository root. - Make the app wait for
infrawithcondition: process_completed_successfully. - Use
process_healthywhen an app waits for another app with a probe.
Put infrastructure services in docker compose profiles:
services:
db:
image: postgres:17
profiles: [infra]
Start them from the infra process:
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.
- 10d ago First seen · 106 lines · 33 tokens per session scan A ce2f7bfe3c53
local-run is a skill published in the GitHub repository me-cedric/agent-compass (3 stars, last pushed 4d ago), licensed MIT. It adds 33 tokens to every session and 1,040 once invoked, about $0.0001 per session on Opus 5.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-10-18.
Other skills, from other repositories
agent-sandbox
Agent skill for sandbox - invoke with $agent-sandbox.
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
cdf-orchestration-setup
Use when the user asks to deploy, install, reinstall, redeploy, upgrade, or connect to the CDF Orchestration Airflow controller. Owns the end-to-end deploy sequence and runs the cdf-orchestration-preflight audit first. Covers make setup, controller image builds, Helm installation, controller connection…
aiq-deploy
Use when asked to install, deploy, run, validate, troubleshoot, or stop NVIDIA AI-Q Blueprint infrastructure.
dynamo-recipe-runner
Select, validate, patch, and deploy existing NVIDIA Dynamo Kubernetes recipes. Use for model/backend/GPU/deployment-mode recipe bring-up; use router-starter for router-only mode work and troubleshoot for broken deployments.
kermt-monitor
Check progress for a detached KERMT run (pretrain, finetune, or any kermtrundetached invocation). Reads run.json, queries docker for container state, tails the pretrain/finetune log, and parses progress lines (epoch, step, val loss).