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 paruff/uFawkesAI --skill unit-core-logicgit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/unit-core-logic)<a href="https://agentmods.dev/skills/paruff/ufawkesai/unit-core-logic"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/unit-core-logic/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/paruff/ufawkesai/unit-core-logic"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/unit-core-logic.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.00039 | $0.00535 |
| Opus 5 | $0.00019 | $0.00267 |
| Sonnet 5 | $0.00008 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
unit-core-logic-testing 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 5d 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
Skill: Unit Core Logic Testing
Load trigger:
"load unit-core-logic-testing skill"> DORA: Cap 5 (Operational Resilience) Token cost: Low
Purpose
Validate pure functions, deterministic logic, and core algorithms in OBS and PIPE.
Responsibilities
- Test DAG evaluation logic
- Validate GitOps parsing and schema validation
- Test error propagation and branching logic
- Ensure deterministic outputs for identical inputs
Inputs
- Source code
- Unit test files
Outputs
junit.xmlcoverage.xml
Test Categories
| Category | Focus | Example |
|---|---|---|
| Pure functions | Input → Output | Version parser, schema validator |
| DAG logic | Ordering, cycles | Pipeline stage ordering |
| Parsing | Format conversion | YAML/JSON parsing, manifest normalization |
| Branching | Conditional logic | Environment-specific behavior |
Performance Thresholds
| Metric | Threshold |
|---|---|
| Test execution | < 200ms per test |
| Coverage | ≥ 80% line coverage |
| Flakiness | 0% (deterministic) |
Validation Rules
- All core logic functions tested
- Deterministic outputs
- No external side effects
- Coverage ≥ 80%
- No tests > 200ms
Tools
- Vitest / Jest
- Pytest (if Python components exist)
- ts-mockito / sinon
Output Format
{
"skill": "unit-core-logic-testing",
"status": "pass | fail",
"total_tests": 150,
"passed": 150,
"failed": 0,
"coverage": {
"line": 85,
"branch": 80,
"function": 90
},
"slow_tests": []
}
Success Criteria
- < 200ms per test
- 80%+ coverage
- No external side effects
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.
- 5d ago First seen · 91 lines · 39 tokens per session scan A daa92926636c
unit-core-logic-testing is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 16d ago), licensed MIT. It adds 39 tokens to every session and 535 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-09-03.
Other skills, from other repositories
template-formal
Strongly-typed multiagent ant-robot colony exemplar — ADTs, session-typed protocols, affine-discipline resource handles, storage-as-functor framing, Active-Inference-flavored decision loop, mypy-as-oracle negative controls.
template-test-creation
Create pytest suites under the no-mocks policy — real data, temp files, subprocess, pytest-httpserver. USE WHEN adding tests, raising coverage, testing new src/ module, or user forbids mocks.
debug-issue
Structured workflow for debugging a reported or reproduced issue. Use when the user asks to debug a bug, find root cause, or fix a failing scenario.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
execution-debugging
Scoped debugging methodology for when a test or build fails during execution/stabilization. Use to diagnose the failing check without scope-creeping — read the full error, reproduce in isolation, hypothesize before changing, localize, fix the root cause not the symptom, and guard with a regression test.
template-code-project
Code-centric optimization research exemplar — gradient descent, convergence analysis, automated figures, dashboard, and publication-quality PDF.