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.
git clone --depth 1 https://github.com/Agentic-Insights/foundryWrote 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/agentic-insights/foundry/baml-test)<a href="https://agentmods.dev/commands/agentic-insights/foundry/baml-test"><img src="https://agentmods.dev/badge/commands/agentic-insights/foundry/baml-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.
<a href="https://agentmods.dev/commands/agentic-insights/foundry/baml-test"><img src="https://agentmods.dev/badge/commands/agentic-insights/foundry/baml-test.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.00000 | $0.00435 |
| Opus 5.5 | $0.00000 | $0.00174 |
| Sonnet 5.5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
baml-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 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
Run BAML Tests
Execute BAML test suite with options.
Quick Usage
# Run all tests
baml-cli test
# Filter by name
baml-cli test --filter "$ARGUMENTS"
# Parallel execution
baml-cli test --parallel 5
# Verbose output
baml-cli test --verbose
Default Behavior
If $ARGUMENTS is empty, run all tests:
baml-cli test
If $ARGUMENTS contains a filter pattern:
baml-cli test --filter "$ARGUMENTS"
Options Parsing
Parse $ARGUMENTS for:
-p Nor--parallel N: Run with N parallel workers-vor--verbose: Show detailed output-f PATTERNor--filter PATTERN: Filter test names- Any other text: Use as filter pattern
Example Commands
/baml-test → baml-cli test
/baml-test Receipt → baml-cli test --filter "Receipt"
/baml-test -p 5 → baml-cli test --parallel 5
/baml-test Receipt -v → baml-cli test --filter "Receipt" --verbose
/baml-test -p 3 -f Extract → baml-cli test --parallel 3 --filter "Extract"
Output Format
Report:
- Command executed
- Test results (pass/fail counts)
- Failure details if any
- Suggestions for failures
On Failure
If tests fail:
- Show which tests failed
- Show assertion that failed
- Show expected vs actual (if available)
- Suggest using
/baml-diagnosefor deeper analysis
Prerequisites
baml_src/directory existsbaml-cliis installed- Environment variables are set
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 · 77 lines · 0 tokens per session scan A 85be083e86e1
baml-test is a command published in the GitHub repository Agentic-Insights/foundry (5 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 435 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-31.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.