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/consiliency/flutter-structurizr/test-implementationgit clone --depth 1 https://github.com/Consiliency/Flutter-StructurizrWhat 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.00000 | $0.00846 |
| Opus 5 | $0.00000 | $0.00423 |
| Sonnet 5 | $0.00000 | $0.00169 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
test-implementation 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Command: Test Latest Implementation
Test Plan Analysis
-
Analyze the testing plan for the current phase:
- Review testing sections in the implemented phase document (
specs/phase{N}_implementation_plan.md) - Check
specs/testing_plan_template.mdfor additional testing guidance - Identify test categories required (unit, widget, integration, golden)
- Note any specific testing frameworks or dependencies needed
- Check for recent test-related best practices and lessons learned in CLAUDE.md and specs/testing_plan.md
- Review testing sections in the implemented phase document (
-
Verify testing environment:
- Check existing test files related to the implemented phase
- Identify test dependencies needed in pubspec.yaml
- Install any missing testing dependencies
- Verify testing utilities and helpers are available
Test Implementation
-
For each implemented feature: Think Hard
- Check if existing tests already cover the functionality
- Create new tests for any untested functionality
- Consider potential name conflicts with Flutter built-ins
- Reference the
ai_doc/directory for specific framework and library documentation - Use Web Fetch, Web Search, and Fetch tools to find examples and documentation if not in
/ai_docs- Compile new documentation that you find into a library specific markdown file and save it in
/ai_docsfor future reference
- Compile new documentation that you find into a library specific markdown file and save it in
- Ensure test coverage for:
- Normal use cases
- Edge cases
- Error handling
- Integration with existing components
-
Follow testing best practices: Ultra Think
- Create unit tests for domain models and application logic
- Implement widget tests for UI components
- Add integration tests for end-to-end functionality
- Create golden tests for visual regression testing when appropriate
- Use mocks and fakes for isolating components
- Handle name conflicts in test files properly (hide directives, alias types)
- Add comments explaining complex test scenarios
-
Run all tests:
- Use the provided testing scripts in the
scripts/directory:scripts/run_all_tests.shto run all testsscripts/run_domain_tests.shfor domain model testsscripts/run_layout_tests.shfor layout testsscripts/run_documentation_tests.shfor documentation testsscripts/run_ui_tests.shfor UI component tests
- Run tests for the specific components implemented
- Run any affected existing tests
- Run flutter test --coverage and report coverage metrics
- Document test results and failures
- Debug and fix any test failures
- Rerun tests until all pass
- If new test strategies or helpers are developed, update the testing plan in specs/
- Document any persistent test failures or workarounds for future developers
- Use the provided testing scripts in the
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.
- 2d ago First seen · 95 lines · 0 tokens per session scan A 6ef58bcf2d06
test-implementation is a command published in the GitHub repository Consiliency/Flutter-Structurizr (7 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 846 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.