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/JSK9999/ai-nexusWrote 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/jsk9999/ai-nexus/test)<a href="https://agentmods.dev/commands/jsk9999/ai-nexus/test"><img src="https://agentmods.dev/badge/commands/jsk9999/ai-nexus/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/jsk9999/ai-nexus/test"><img src="https://agentmods.dev/badge/commands/jsk9999/ai-nexus/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.00004 | $0.00288 |
| Opus 5.5 | $0.00002 | $0.00115 |
| Sonnet 5.5 | $0.00001 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
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
/test
When asked to write tests:
- Read the source — Understand what the code does before writing tests
- Identify cases — Happy path, edge cases, error cases
- Write tests — Use AAA pattern (Arrange, Act, Assert)
- Run tests — Verify they pass
- Check coverage — Ensure critical paths are covered
Test Structure
describe('functionName', () => {
it('should return X when given Y', () => {
// Arrange
const input = createInput();
// Act
const result = functionName(input);
// Assert
expect(result).toBe(expected);
});
it('should throw when input is invalid', () => {
expect(() => functionName(null)).toThrow();
});
});
What to Cover
- Normal inputs → expected outputs
- Empty/null/undefined inputs
- Boundary values (0, -1, MAX)
- Error conditions and exceptions
- Async operations (resolve and reject)
Rules
- One assertion per test (when practical)
- No test interdependence — each test runs independently
- Use descriptive names: "should [expected] when [condition]"
- Don't test private/internal methods directly
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 · 48 lines · 4 tokens per session scan A e36e62281bb4
test is a command published in the GitHub repository JSK9999/ai-nexus (19 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 4 tokens to every session and 288 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
assess
Ground one dependency-update request against this repository as it exists right now, and decide whether an update is actually owed. You produce an assessment and a verdict; you change nothing. No one watches the run; the assessment file and your declared fields are the only things that persist.
maintainer-review-test-coverage
Review the PR for test coverage — does new behavior have tests, are critical paths exercised, do existing tests still cover what they should (Pi-tuned).
review-tests
Find this class of defect: the change establishes or alters meaningful behavior, and no test would fail when that behavior regresses in a plausible way. Tests protect outcomes and invariants — count, lines, and coverage percentages are not outcomes. Not every change needs a test, and a change with none is not a…
discover-checks
Find the project's own checks and declare them. You do not run the gate: a script runs exactly what you declare, for as long as it takes, and records every exit status. Your declaration is the whole of what gets validated, so it must be the project's gate and nothing else.
classify-red
The project's gate ran and at least one check failed. $ARTIFACTSDIR/validation.md is the record: every check that ran, its group, its exit status, each failing check's output tail, and the path of each check's full output log. Decide why the failed checks failed, judging every one the record names. You fix nothing and…
e2e-echo-command
E2E test command — echoes back the user message.