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 LuizEduPP/Rememb --skill test-creategit clone --depth 1 https://github.com/LuizEduPP/RemembWrote 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/luizedupp/rememb/test-create)<a href="https://agentmods.dev/skills/luizedupp/rememb/test-create"><img src="https://agentmods.dev/badge/skills/luizedupp/rememb/test-create/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/luizedupp/rememb/test-create"><img src="https://agentmods.dev/badge/skills/luizedupp/rememb/test-create.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.00023 | $0.00527 |
| Opus 5.5 | $0.00009 | $0.00211 |
| Sonnet 5.5 | $0.00005 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
test-create 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Tests
Generate comprehensive test cases for code.
Overview
Use this skill to draft focused tests that cover behavior, edge cases, and failures without coupling the tests to implementation details.
When to Use
- Writing new unit tests
- Adding integration or acceptance coverage
- Reproducing a bug with a failing test first
- Checking whether a change has enough verification
Quick Start
- Identify the behavior or acceptance criterion
- Add one happy-path test
- Add the most important edge case
- Add the failure mode or invalid input case
- Run the narrowest possible test command first
Test Categories
| Category | Examples |
|---|---|
| ✅ Happy Path | Normal inputs, standard cases |
| 🔸 Edge Cases | Empty, boundary, min/max |
| ❌ Error Cases | Invalid inputs, failures |
Python (pytest)
import pytest
class TestFunction:
def test_valid_input_returns_expected(self):
assert function("valid") == "expected"
def test_empty_input_returns_empty(self):
assert function("") == ""
def test_invalid_raises_error(self):
with pytest.raises(ValueError):
function(None)
JavaScript (Jest)
describe('function', () => {
it('returns expected for valid input', () => {
expect(fn('valid')).toBe('expected');
});
it('handles empty input', () => {
expect(fn('')).toBe('');
});
it('throws for invalid', () => {
expect(() => fn(null)).toThrow();
});
});
Naming Convention
test_[what]_[condition]_[expected]
test_login_valid_credentials_returns_token
test_login_wrong_password_raises_error
Coverage Goals
| Type | Target |
|---|---|
| Business logic | 80%+ |
| Utilities | 90%+ |
| UI | 60%+ |
Best Practices
- Test behavior, not implementation
- One assertion per test
- Mock external dependencies
- Keep tests fast
Core Workflow
Follow the primary workflow, commands, and decision points documented in the sections below.
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 · 106 lines · 23 tokens per session scan A 58d14fb1b045
test-create is a skill published in the GitHub repository LuizEduPP/Rememb (5 stars, last pushed 12d ago), licensed MIT. It adds 23 tokens to every session and 527 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-08-31.
Other skills, from other repositories
test-runner
For a code change, pick the right test tier by change surface, run apc test with baseline diff, and report only NEW reds vs baseline back to the task's acceptance criterion. Separates envblocked from SUT red so a broken machine never fails the code.
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
mockito
Use when generating mocks, stubbing methods, verifying interactions, capturing arguments, or choosing between mocks, fakes, and real objects (Mockito).
mocktail
Use when creating mocks, stubbing methods, verifying interactions, registering fallback values, or choosing between mocks, fakes, and real objects (Mocktail).
pn-testing-strategy
Testing strategy and pyramid. Unit/integration/E2E ratio, Vitest vs Playwright vs MSW, contract testing, and test-environment setup. Use when defining or reviewing a project's testing approach.
pn-test-generation
Generate unit or integration tests from code, specs, or acceptance criteria. Use when adding test coverage, scaffolding TDD, or backfilling tests for existing code.