skill-thiientv-godmode-test-strategy · by Install
$ agentstack add skill-thiientv-godmode-test-strategy ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-thiientv-godmode-test-strategy) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Test Strategy
Coverage is a means; risk and failure detection are the decision criteria.
Strategy loop
- Identify critical user journeys, assets, contracts, dependencies, and recent
change areas.
- Score impact and likelihood; include data loss, privacy, money, access,
safety, operational, and reputation failure modes.
- Map each high-risk item to the cheapest test level that reaches the real
failure: unit, contract, integration, component, browser, load, security, exploratory, or production monitoring.
- Define fixtures, environment parity, deterministic data, test ownership,
test oracle, and cleanup.
- Set release gates and explicit exclusions. Include negative, boundary,
retry, concurrency, migration, accessibility, and recovery paths when risk warrants them.
- Reassess after incidents, architecture changes, dependency changes, and
high-churn releases.
Choose specialized test modes
- Use exploratory charters when risks or failure shapes are not understood;
time-box the session, record observations, then convert repeatable discoveries into automated checks.
- Use contract tests at independently deployed consumer/provider seams;
verify compatibility before deployment rather than duplicating implementation tests on both sides.
- Classify flaky tests by product race, test race, data, environment,
dependency, resource contention, or selector drift. Quarantine only with an owner, evidence, expiry, and a still-visible signal; retries are not a fix.
- Use production tests only with non-destructive synthetic identities,
blast-radius controls, monitoring, cleanup, and a tested abort path.
- Use agent evaluation for stochastic model-backed behavior; ordinary pass
rates and snapshots do not capture variance, tool trajectory, cost, or grounding.
Read [risk-matrix.md](references/risk-matrix.md) and [specialized-modes.md](references/specialized-modes.md). Avoid a universal coverage percentage, brittle snapshots with no oracle, and tests that pass only because they mock the behavior under test.
Completion condition
The strategy connects risk to an executable check, names ownership and test data, defines release gates, and makes untested risk visible.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: thiientv
- Source: thiientv/godmode
- License: MIT
- Homepage: https://thiientv.github.io/godmode
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.