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/samplexbro/agentsmesh/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/commands/samplexbro/agentsmesh/build)<a href="https://agentmods.dev/commands/samplexbro/agentsmesh/build"><img src="https://agentmods.dev/badge/commands/samplexbro/agentsmesh/build.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.00014 | $0.00161 |
| Opus 5 | $0.00007 | $0.00081 |
| Sonnet 5 | $0.00003 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
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 yesterday.
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.
This is a copy
100% identical to build — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- yesterday First seen · 19 lines · 14 tokens per session scan A 93754af699d8
build is a command published in the GitHub repository sampleXbro/agentsmesh (24 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 161 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to build, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
commit
Create a local git commit for source skills without pushing.
summarize-changes
Summarize recent changes for standup, PR, or documentation.
api-aqa-flow
Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.
spec-impl
Execute spec tasks using TDD methodology.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.