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 agentmods add skills/jnzader/repoforge/test_graphnpx skills add JNZader/repoforge --skill test_graphgit clone --depth 1 https://github.com/JNZader/repoforgeWrote 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/jnzader/repoforge/test_graph)<a href="https://agentmods.dev/skills/jnzader/repoforge/test_graph"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/test_graph.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 | $0.00030 | $0.00475 |
| Opus 5 | $0.00015 | $0.00237 |
| Sonnet 5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
mock-repomaps-fixtures 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 4d 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
Mock RepoMaps Fixtures
This skill covers patterns for mocking RepoMaps in tests.
Trigger: Load this skill when working with test_graph fixtures.
Quick Reference
| Task | Pattern |
|---|---|
| Create a small graph fixture | small_graph |
| Test adding a node | TestAddNode |
Critical Patterns (Summary)
- small_graph: Provides a predefined small graph for testing.
- TestAddNode: Tests the functionality of adding a node to the graph.
Critical Patterns (Detailed)
small_graph
This pattern provides a predefined small graph for testing purposes, allowing for consistent and repeatable tests.
# Example usage of small_graph
from tests.test_graph import small_graph
def test_small_graph():
assert len(small_graph.nodes) == expected_node_count
TestAddNode
This pattern tests the functionality of adding a node to the graph, ensuring that the graph updates correctly.
# Example usage of TestAddNode
from tests.test_graph import TestAddNode
def test_add_node():
test_case = TestAddNode()
test_case.run()
When to Use
- When you need to create a small graph for unit tests.
- When testing the addition of nodes to a graph structure.
Commands
pytest tests/test_graph.py
Anti-Patterns
Don't: Use real RepoMaps in tests
Using real RepoMaps can lead to flaky tests and inconsistent results.
# BAD
from repo.maps import RepoMap
def test_with_real_repos():
repo = RepoMap()
assert repo is not None
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.
- 4d ago First seen · 91 lines · 30 tokens per session scan A 9a4d05855a68
mock-repomaps-fixtures is a skill published in the GitHub repository JNZader/repoforge (5 stars, last pushed 10d ago), licensed MIT. It adds 30 tokens to every session and 475 once invoked, about $0.0002 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-31.
Other skills, from other repositories
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
write-sglang-test
Guide for writing SGLang CI/UT tests. Covers CustomTestCase, CI registration, server fixtures, model selection, mock testing, and test placement. Always read test/README.md for the full CI layout, how to run tests, and extra tips. Use when creating new tests, adding CI test cases, writing unit tests, or when the user…
testing
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
add-unit-tests
Guide for adding unit tests to AReaL. Use when user wants to add tests for new functionality or increase test coverage.
neuron-test-engineer
Write tests for Neuron AI agents, RAG systems, workflows, and tools using the built-in testing utilities. Use this skill when the user mentions testing agents, writing unit tests, mocking AI providers, testing tool execution, verifying RAG retrieval, testing workflow behavior, or creating test cases for Neuron AI…
js-in-html-testing
Test JS logic embedded in HTML using two-layer strategy - Python unit tests + Playwright browser integration tests.