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 ArabelaTso/Skills-4-SE --skill assertion-synthesizergit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/assertion-synthesizer)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/assertion-synthesizer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/assertion-synthesizer/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/arabelatso/skills-4-se/assertion-synthesizer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/assertion-synthesizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00087 | $0.02735 |
| Opus 5 | $0.00044 | $0.01367 |
| Sonnet 5 | $0.00017 | $0.00547 |
| Haiku 4.5 | $0.00009 | $0.00274 |
Grade A, and why
assertion-synthesizer 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 12d 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 — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assertion Synthesizer
Generate comprehensive test assertions by analyzing code implementation, behavior, and expected outputs.
Workflow
1. Analyze Code
Read and understand the implementation to identify testable behavior:
- Function signatures: Parameters, return types, side effects
- Logic paths: Conditionals, loops, branching behavior
- Edge cases: Boundary conditions, null/empty inputs, error conditions
- State changes: Object mutations, attribute modifications
- Dependencies: External calls, database operations, I/O
2. Identify Test Scenarios
Extract scenarios that need assertions:
- Happy path: Normal inputs producing expected outputs
- Edge cases: Empty lists, zero values, boundary conditions
- Error cases: Invalid inputs, exceptions, error handling
- State verification: Object state before/after operations
- Collection assertions: List contents, ordering, membership
3. Generate Assertions
Create appropriate assertions for each scenario:
Assertion Types:
- Equality:
assert result == expected,assertEquals(expected, actual) - Truthiness:
assert is_valid,assertTrue(condition) - Collections:
assert item in list,assertContains(list, item) - Exceptions:
pytest.raises(Exception),assertThrows(Exception) - State:
assert obj.status == "active",assertEquals("active", obj.getStatus())
4. Structure Tests
Organize assertions into well-structured test functions:
- Use descriptive test names
- Follow Arrange-Act-Assert pattern
- Group related assertions
- Add explanatory comments
5. Verify Coverage
Ensure all important behaviors have assertions:
- Check all return values are tested
- Verify edge cases are covered
- Confirm error conditions are tested
- Validate state changes are asserted
Language-Specific Patterns
Python (pytest)
def test_basic_equality():
# Arrange
calculator = Calculator()
# Act
result = calculator.add(2, 3)
# Assert
assert result == 5
def test_collection_membership():
items = get_active_items()
assert "item1" in items
assert len(items) == 3
def test_exception_handling():
with pytest.raises(ValueError, match="Invalid input"):
process_data(None)
def test_state_change():
user = User("Alice")
user.activate()
assert user.is_active == True
assert user.status == "active"
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.
- 12d ago First seen · 443 lines · 87 tokens per session scan A 4de8311f8770
assertion-synthesizer is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (252 stars, last pushed 22d ago), licensed Apache-2.0. It adds 87 tokens to every session and 2,735 once invoked, about $0.0004 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 skills, from other repositories
review-ugc-render
Mandatory pre-publish review gate for a UGC video render. Transcribes the finished render's AUDIO with Whisper and word-diffs it against the approved spoken script, then gates setfinalrender — blocking a render whose generated audio mis-voices a word (e.g. the approved "human-vetted" spoken as "human witted"), drops…
test-generator
A test-writing helper that creates unit or integration tests from the code's actual behavior and contracts. Unit tests check small pieces of code, while integration tests check how real components work together.
testing-r-packages
Best practices for writing R package tests using testthat version 3+. Use when writing, organizing, or improving tests for R packages. Covers test structure, expectations, fixtures, snapshots, mocking, and modern testthat 3 patterns including self-sufficient tests, proper cleanup with withr, and snapshot testing.
r-package-development
R package development with devtools, testthat, and roxygen2. Use when the user is working on an R package, running tests, writing documentation, or building package infrastructure.
111-java-maven-dependencies
Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a…
130-java-testing-strategies
Use when you need to apply testing strategies for Java code — RIGHT-BICEP to guide test creation, A-TRIP for test quality characteristics, or CORRECT for verifying boundary conditions. This should trigger for requests such as Review Java code for testing strategies; Apply RIGHT-BICEP testing strategies in Java code…