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 sampleXbro/agentsmesh --skill am-command-buildgit clone --depth 1 https://github.com/sampleXbro/agentsmeshWrote 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/samplexbro/agentsmesh/am-command-build)<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/am-command-build"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/am-command-build/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/samplexbro/agentsmesh/am-command-build"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/am-command-build.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.00018 | $0.00183 |
| Opus 5.5 | $0.00007 | $0.00073 |
| Sonnet 5.5 | $0.00004 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
am-command-build 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 1mo 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
Invoke the agent-skills:incremental-implementation skill alongside agent-skills:test-driven-development.
Pick the next pending task from the plan. For each task:
- Read the task's acceptance criteria
- Load relevant context (existing code, patterns, types)
- Write a failing test for the expected behavior (RED)
- Implement the minimum code to pass the test (GREEN)
- Run the full test suite to check for regressions
- Run the build to verify compilation
- Commit with a descriptive message
- Mark the task complete and move to the next one
If any step fails, follow the agent-skills:debugging-and-error-recovery skill.
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.
- 1mo ago First seen · 21 lines · 18 tokens per session scan A 76469bbab2f2
am-command-build is a skill published in the GitHub repository sampleXbro/agentsmesh (25 stars, last pushed 22d ago), licensed MIT. It adds 18 tokens to every session and 183 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-08-30.
Other skills, from other repositories
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
test-then-commit
Implements a small change and commits it. Use when the user asks for a quick fix with a commit.
tdd
Enforces red-green-refactor TDD cycle with atomic commits per phase. Used when implementing features, fixing bugs, or when tests should drive the design.
Changelog Test Mapper
Map changelog entries and release notes to affected test cases, ensuring every user-facing change has corresponding test coverage verification.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.
cmux-testing
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.