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/postindustria-tech/agentic-toolkitWrote 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/postindustria-tech/agentic-toolkit/create-tests)<a href="https://agentmods.dev/commands/postindustria-tech/agentic-toolkit/create-tests"><img src="https://agentmods.dev/badge/commands/postindustria-tech/agentic-toolkit/create-tests/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/postindustria-tech/agentic-toolkit/create-tests"><img src="https://agentmods.dev/badge/commands/postindustria-tech/agentic-toolkit/create-tests.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.00016 | $0.00838 |
| Opus 5.5 | $0.00006 | $0.00335 |
| Sonnet 5.5 | $0.00003 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
create-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 10d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Test Suite for LangGraph
Generate comprehensive pytest tests for LangGraph workflows including state tests, node unit tests, and integration tests with mocked LLMs.
Instructions for Claude
1. Analyze Target Graph
Read the graph file to identify:
- State schema (TypedDict definition)
- Node functions
- Edge connections
- Conditional routing logic
Use Grep to find:
- State class definition
- Node function definitions
workflow.add_node()callsworkflow.add_edge()andworkflow.add_conditional_edges()calls
2. Gather Test Requirements
Ask user:
- Coverage level (basic or comprehensive)
- Whether to mock LLM calls (default: yes)
- Whether to generate integration tests (default: yes)
3. Generate Test Structure
Create:
tests/
├── __init__.py
├── conftest.py # Fixtures
├── test_state.py # State schema tests
├── test_nodes.py # Node unit tests
├── test_graph.py # Integration tests
└── fixtures/
└── mock_data.py # Test data
4. Generate conftest.py
import pytest
from unittest.mock import Mock
@pytest.fixture
def mock_llm():
\"\"\"Mock LLM for testing.\"\"\"
mock = Mock()
mock.invoke.return_value = Mock(content="Mocked response")
return mock
@pytest.fixture
def sample_state():
\"\"\"Sample state for testing.\"\"\"
return {
"messages": [],
"current_step": "start"
}
5. Generate test_state.py
from src.state import {StateName}
def test_state_structure():
\"\"\"Test state accepts valid data.\"\"\"
state = {StateName}(
messages=[],
current_step="start"
)
assert isinstance(state["messages"], list)
def test_state_validation():
\"\"\"Test state validation logic.\"\"\"
# Add validation tests
6. Generate test_nodes.py
For each node, create:
def test_{node_name}(mock_llm, monkeypatch, sample_state):
\"\"\"Test {node_name} node with mocked LLM.\"\"\"
monkeypatch.setattr('src.nodes.llm', mock_llm)
result = {node_name}(sample_state)
assert "expected_field" in result
mock_llm.invoke.assert_called_once()
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.
- 10d ago First seen · 154 lines · 16 tokens per session scan A e769b9dd1f87
create-tests is a command published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 11d ago), licensed MIT. It adds 16 tokens to every session and 838 once invoked, about $0.0001 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-10-06.
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.
story-and-test
For the component(s) in scope.
test
Execute a comprehensive test run for the following target.
frappe-test
Run unit and integration tests for Frappe apps with coverage reports.