A command that builds a Rust project in release mode and runs its tests. It can also run only tests matching a pattern supplied by the user.

Use it before handing off Rust changes, when validating a release build, or when investigating failures in the full test suite or a selected group of tests.

It checks whether the project compiles and its automated tests pass in one cycle. When something fails, it reports the failed test, what it covered, the likely cause, and a possible fix.

How notactuallytreyanastasio/deciduous configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to notactuallytreyanastasio/deciduous. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/notactuallytreyanastasio/deciduous/main/.claude/commands/build-test.md

Clone the repo

git clone --depth 1 https://github.com/notactuallytreyanastasio/deciduous

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/notactuallytreyanastasio/deciduous/build-test/github.svg)](https://agentmods.dev/commands/notactuallytreyanastasio/deciduous/build-test)

Your own site

<a href="https://agentmods.dev/commands/notactuallytreyanastasio/deciduous/build-test"><img src="https://agentmods.dev/badge/commands/notactuallytreyanastasio/deciduous/build-test/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/notactuallytreyanastasio/deciduous/build-test"><img src="https://agentmods.dev/badge/commands/notactuallytreyanastasio/deciduous/build-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 131 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.00131
Opus 5.5	$0.00000	$0.00052
Sonnet 5.5	$0.00000	$0.00026
Haiku 4.5	$0.00000	$0.00013

Measured 2mo ago against content hash b3c62f4f86fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

build-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 2mo 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.

.claude/commands/build-test.md · 26 lines

What it actually says

Build and Test

Build the project and run the test suite.

Instructions

Run the full build and test cycle:
```
cargo build --release && cargo test
```
If tests fail, analyze the failures and explain:
- Which test failed
- What it was testing
- Likely cause of failure
- Suggested fix
If all tests pass, report success and any warnings from the build.
If the user specifies a specific test pattern, run only those tests:
```
cargo test <pattern>
```

$ARGUMENTS

Changes

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.

2mo ago First seen · 26 lines · 0 tokens per session scan A b3c62f4f86fe

Subscribe to this mod's changes

build-test is a command published in the GitHub repository notactuallytreyanastasio/deciduous (169 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 131 tokens. 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.

Testing

build-test next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
build-testnotactuallytreyanastasio/deciduous	Command	169	13d ago	Apache-2.0	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

deciduous: Command for Claude Code