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/thapaliyabikendra/ai-artifactsWrote 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/thapaliyabikendra/ai-artifacts/generate-tests)<a href="https://agentmods.dev/commands/thapaliyabikendra/ai-artifacts/generate-tests"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/generate-tests.svg" alt="Measured on agentmods" 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.00015 | $0.01643 |
| Opus 5 | $0.00008 | $0.00822 |
| Sonnet 5 | $0.00003 | $0.00329 |
| Haiku 4.5 | $0.00002 | $0.00164 |
Grade A, and why
generate-tests 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 7d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Tests
Generate tests for: $ARGUMENTS.target Test type: $ARGUMENTS.type Dry run: $ARGUMENTS.dry-run
Instructions
Step 1: Identify Target
If target is 'gaps':
- Run coverage analysis (see
/qa:coverage-report) - Identify top 5 files without tests
- Generate tests for each
If target is file path:
- Read the source file
- Parse public methods and their signatures
- Identify validators if any
If target is class name:
- Search for the class in
api/src/ - Read the source file
Step 2: Analyze Source Code
For each public method, extract:
- Method name
- Parameters and types
- Return type
- Dependencies (injected services)
- Validation rules (if validator)
- Authorization attributes
Step 3: Generate Unit Tests
For AppServices:
using Shouldly;
using Xunit;
using NSubstitute;
namespace [Namespace].Tests;
public class [ClassName]Tests : [Module]ApplicationTestBase
{
private readonly [ClassName] _sut;
private readonly I[Dependency] _[dependency];
public [ClassName]Tests()
{
_[dependency] = Substitute.For<I[Dependency]>();
_sut = new [ClassName](_[dependency]);
}
#region [MethodName]
[Fact]
public async Task [MethodName]_ValidInput_ReturnsExpectedResult()
{
// Arrange
var input = new [InputDto]
{
// Set valid properties
};
// Act
var result = await _sut.[MethodName](input);
// Assert
result.ShouldNotBeNull();
}
[Fact]
public async Task [MethodName]_InvalidInput_ThrowsValidationException()
{
// Arrange
var input = new [InputDto](); // Missing required fields
// Act & Assert
await Should.ThrowAsync<AbpValidationException>(
() => _sut.[MethodName](input)
);
}
[Fact]
public async Task [MethodName]_NotFound_ThrowsEntityNotFoundException()
{
// Arrange
var nonExistentId = Guid.NewGuid();
// Act & Assert
await Should.ThrowAsync<EntityNotFoundException>(
() => _sut.[MethodName](nonExistentId)
);
}
#endregion
}
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.
- 7d ago First seen · 283 lines · 15 tokens per session scan A 40d952dfb67c
generate-tests is a command published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 1,643 once invoked, about $0.0001 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 commands, from other repositories
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
lg:node
Create, modify, and manage nodes in LangGraph graphs including LLM nodes, tool nodes, human-in-the-loop, subgraphs, and conditional nodes.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
test
Execute a comprehensive test run for the following target.
frappe-test
Run unit and integration tests for Frappe apps with coverage reports.