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 skills add prime-radiant-inc/greenfield --skill test-suite-analysisgit clone --depth 1 https://github.com/prime-radiant-inc/greenfieldWrote 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/skills/prime-radiant-inc/greenfield/test-suite-analysis)<a href="https://agentmods.dev/skills/prime-radiant-inc/greenfield/test-suite-analysis"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/greenfield/test-suite-analysis/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/skills/prime-radiant-inc/greenfield/test-suite-analysis"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/greenfield/test-suite-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 229 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium MCP Rug Pull · line 177 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 201 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 204 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00057 | $0.03049 |
| Opus 5 | $0.00028 | $0.01524 |
| Sonnet 5 | $0.00011 | $0.00610 |
| Haiku 4.5 | $0.00006 | $0.00305 |
Grade A, and why
test-suite-analysis 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 11d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Suite Analysis Methodology
Extract behavioral intelligence from test suites. Tests are executable specifications -- they encode what the system MUST do in a form that can be verified. A passing test is a confirmed behavioral contract.
When to Use This Mode
Test suite analysis activates when:
- The target repository contains test files
- The discovery inventory identifies test files in the project
- Other modes discover test directories during analysis
This mode runs independently of all other intelligence sources. All output is RAW (test code references internal implementation details).
Why Tests Are High-Value Intelligence
Tests are the only source type that is simultaneously:
- Behavioral -- they describe what the system does, not how it's built
- Executable -- they can be run to confirm the behavior still holds
- Specific -- they provide exact inputs, expected outputs, and edge cases
- Maintained -- failing tests get fixed, so they track current behavior
A single end-to-end test is worth more than a page of documentation because the test is verified by CI on every commit.
Framework Detection
Identify the test framework(s) in use before analyzing test code. Different frameworks use different assertion styles, test organization, and execution models.
| Framework | Language | Detection Signals |
|---|---|---|
| Jest | JavaScript/TypeScript | jest.config.*, describe( / it( / expect( in __tests__/ or *.test.*, @jest/globals imports |
| Playwright | JavaScript/TypeScript | playwright.config.*, @playwright/test imports, page.goto( / page.click( |
| Cypress | JavaScript/TypeScript | cypress.config.*, cypress/ directory, cy.visit( / cy.get( |
| pytest | Python | conftest.py, pytest.ini / pyproject.toml with [tool.pytest], files named test_*.py / *_test.py, assert statements |
| Go testing | Go | *_test.go files, testing.T / testing.B parameters, go test in CI config |
| RSpec | Ruby | .rspec, spec/ directory, spec_helper.rb, describe / it / expect blocks |
| JUnit | Java/Kotlin | @Test annotations, src/test/ directory, assertEquals / assertThat calls |
| XCTest | Swift/Objective-C | XCTestCase subclasses, func test*() methods, XCTAssert* calls |
| Catch2 | C++ | #include <catch2/catch.hpp>, TEST_CASE( / SECTION( / REQUIRE( macros |
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.
- 11d ago First seen · 267 lines · 57 tokens per session scan A 4d998b19aee6
test-suite-analysis is a skill published in the GitHub repository prime-radiant-inc/greenfield (275 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 3,049 once invoked, about $0.0003 per session on Opus 5. 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 skills, from other repositories
write-test-plans
Interactive workflow for writing new Speky test plans for requirements lacking coverage, guided by the Speky MCP server.
speky-workflow
Guidelines for working with Speky requirements and tests via the speky MCP server tools.
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
validate-album
Validates album directory structure, file locations, and content integrity. Use before release or whenever the user wants to check an album's structural health.
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
bun-jest-migration
Use when migrating from Jest to Bun's test runner, import compatibility, mocks, and config.