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/hoangsonww/Forge-Agentic-Coding-CLIWrote 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/rules/hoangsonww/forge-agentic-coding-cli/testing)<a href="https://agentmods.dev/rules/hoangsonww/forge-agentic-coding-cli/testing"><img src="https://agentmods.dev/badge/rules/hoangsonww/forge-agentic-coding-cli/testing/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/rules/hoangsonww/forge-agentic-coding-cli/testing"><img src="https://agentmods.dev/badge/rules/hoangsonww/forge-agentic-coding-cli/testing.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.00242 |
| Opus 5.5 | $0.00000 | $0.00097 |
| Sonnet 5.5 | $0.00000 | $0.00048 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
testing 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
Testing rules
- Runner: vitest. Run one file:
npx vitest run test/unit/<file>.test.ts. - 249 tests across 43 files must remain 100% green. Never
.only, skip, or comment out a test to make the suite pass. - Never make real network calls in unit tests. Mock with
vi.mock. Seetest/unit/executor-loop.test.tsfor thecallModelstub andtest/unit/adapter.test.tsfor the provider stub. - Use tempdirs (
os.tmpdir()+fs.mkdtempSync) for disk writes; clean up inafterEach. Seetest/unit/validation-gate.test.ts. - Test names describe behaviour: "should reject task when provider is unreachable", not "calls provider.ping once".
- New logic in
src/core,src/agents, orsrc/toolsrequires a unit test — not optional.
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 · 24 lines · 0 tokens per session scan A 4088eb20a4c8
testing is a cursor rule published in the GitHub repository hoangsonww/Forge-Agentic-Coding-CLI (26 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 242 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.
Other cursor rules, from other repositories
pytest_unit_test_rules
Pytest Unit Test Rules for this repository.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
ai-actions-test-data
Each action defined in actions.json must have a corresponding server/testdata/ .json test fixture. A missing server/testdata/ directory or any missing fixture is a blocking issue.
testing
Guide for writing pytest unit and integration tests.
pytest-what-to-test-and-mocking
We mock external API calls (mark live tests with @pytest.mark.flaky()). We reuse fixtures from conftest.py. We always use pytest as testing framework - never import unittest. We use pytest-mock (mocker fixture) and monkeypatch for mocking, not unittest.mock.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.