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/joinwell52-ai/codeflowmu-open/run-local-command-checknpx skills add joinwell52-AI/CodeFlowMu-open --skill run-local-command-checkgit clone --depth 1 https://github.com/joinwell52-AI/CodeFlowMu-openWrote 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/joinwell52-ai/codeflowmu-open/run-local-command-check)<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/run-local-command-check"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/run-local-command-check.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.00039 | $0.00313 |
| Opus 5 | $0.00019 | $0.00156 |
| Sonnet 5 | $0.00008 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00031 |
Grade A, and why
run-local-command-check 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 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.
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.
What it actually says
Run Local Command Check
When to use
Use before running commands that produce evidence for a task, especially tests, typechecks, builds, local scripts, CLI diagnostics, or health checks.
Rules
- State the command purpose before relying on its output.
- Prefer the smallest command that verifies the claim.
- Run commands from the correct workspace directory.
- Capture the command, exit status, and key output.
- Treat failure output as evidence, not as something to hide.
- Do not claim success if a command failed or was not run.
- Avoid destructive commands unless the task explicitly authorizes them.
Required output
When reporting, include:
- Command.
- Working directory.
- Result: pass, fail, skipped, or blocked.
- Key output lines or a concise summary.
- Any follow-up risk from skipped checks.
Forbidden actions
- Do not fabricate command output.
- Do not run broad or slow checks when a narrow check is enough unless risk justifies it.
- Do not use command success alone as proof of UI or product correctness when browser or manual behavior matters.
Minimal example
Command: npm --prefix packages/codeflowmu-runtime test
Purpose: verify runtime unit tests after router change
Result: pass
Evidence: 280 tests passed, 0 failed
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 · 47 lines · 39 tokens per session scan A 2b285208914d
run-local-command-check is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 11d ago), licensed MIT. It adds 39 tokens to every session and 313 once invoked, about $0.0002 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-31.
Other skills, from other repositories
agentbro-release
Use when releasing AgentBro from this repository: merging dev/main, bumping versions, updating release notes, tagging, pushing, monitoring GitHub Actions, Homebrew cask publication, or fixing a bad release.
agentbro-pr-merge
Use when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution matters.
source-command-check
跑全套本地校验(前端 lint/test/build + Rust check)。.
oculpm-journal
MCP 도구가 보이면 이 스킬 대신 도구를 쓴다 — journalwrite / planstatus / planupdate 가 경로·파일명·frontmatter 규격을 서버에서 보장한다. 아래는 도구가 없을 때 파일을 직접 쓰는 규격이다.
self-audit
작업을 "완료"라고 보고하기 직전, 스스로 결과를 감사할 때. 커밋/PR 직전 최종 점검에도 사용.
project-inception
Use when kicking off a new project or feature area in an ocul-pm tracked project (.oculpm/ present) — research the stack landscape via web search, then converse with the user (research-backed choices) to settle the optimal spec, and seed a discussion doc, a detailed 3-depth plan (plancreate), EVALS.md done-criteria…