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/sowiedu/edict/edict-testingnpx skills add Sowiedu/Edict --skill edict-testinggit clone --depth 1 https://github.com/Sowiedu/EdictWrote 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/sowiedu/edict/edict-testing)<a href="https://agentmods.dev/skills/sowiedu/edict/edict-testing"><img src="https://agentmods.dev/badge/skills/sowiedu/edict/edict-testing.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.00085 | $0.01445 |
| Opus 5 | $0.00043 | $0.00723 |
| Sonnet 5 | $0.00017 | $0.00289 |
| Haiku 4.5 | $0.00009 | $0.00145 |
Grade A, and why
edict-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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edict Testing
Edict uses vitest for testing. The test suite covers all 6 pipeline stages plus MCP integration.
Commands
npm test # Run all tests (vitest run)
npm run test:watch # Watch mode (vitest)
npm run test:coverage # Coverage report (vitest run --coverage)
Directory Structure
tests/
├── validator/ # Phase 1: Schema validation
│ ├── valid-programs.test.ts # Valid ASTs that should pass
│ ├── invalid-programs.test.ts # Invalid ASTs that should fail with specific errors
│ ├── edge-cases.test.ts # Boundary conditions
│ └── examples.test.ts # All example programs validate
├── resolver/ # Phase 2a: Name resolution
│ ├── resolve.test.ts # Core resolution tests
│ ├── coverage.test.ts # Additional coverage
│ └── coverage-extended.test.ts # Extended edge cases
├── checker/ # Phase 2b: Type checking
│ ├── check.test.ts # Core type checking tests
│ ├── coverage.test.ts # Additional coverage
│ └── coverage-extended.test.ts # Extended edge cases
├── effects/ # Phase 3: Effect checking
│ ├── effect-check.test.ts # Effect propagation and violation tests
│ └── call-graph.test.ts # Call graph construction
├── contracts/ # Phase 4: Contract verification
│ ├── verify.test.ts # Z3 contract verification
│ └── translate.test.ts # Expression → Z3 translation
├── codegen/ # Phase 5: WASM code generation
│ ├── codegen.test.ts # AST → WASM compilation
│ ├── runner.test.ts # WASM execution
│ ├── e2e.test.ts # End-to-end compile + run
│ └── string-table.test.ts # String interning
├── errors/ # Error system
│ └── fix-suggestions.test.ts # Fix suggestion generation
├── mcp/ # Phase 6: MCP server
│ ├── handlers.test.ts # Tool handler tests
│ ├── agent-simulation.test.ts # Simulated agent session
│ ├── http-transport.test.ts # HTTP/SSE transport
│ └── version.test.ts # Version tool
└── pipeline/ # Full pipeline
└── check.test.ts # End-to-end check pipeline
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 · 166 lines · 85 tokens per session scan A b75bc238a3c3
edict-testing is a skill published in the GitHub repository Sowiedu/Edict (11 stars, last pushed 6d ago), licensed MIT. It adds 85 tokens to every session and 1,445 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
automatic-differentiation-advanced
Extend Sounio's automatic differentiation capabilities to higher‑order derivatives, Hessians, differentiation through control flow, and GPU‑accelerated gradient computation, enabling state‑of‑the‑art scientific machine learning.
epistemic-uncertainty-quantification
Extend Sounio's epistemic types with advanced uncertainty quantification methods, such as confidence intervals, non‑Gaussian distributions, and Dempster‑Shafer evidence combination, positioning the language at the state‑of‑the‑art in measurement science.
formal-verification-epistemic
Integrate formal verification tools (SMT solvers, Lean) to prove properties of epistemic programs, such as uncertainty bounds, confidence guarantees, and provenance integrity, establishing Sounio as a language with mathematically verified scientific claims.
sounio-pgo
Work on the profile-guided optimization pipeline: counter injection, .sprof file output, strategy promotion, inlining, layout, const-fold/DCE, and register allocation; use when editing any sprint 38–52+ IR optimization files.
safe-refactoring
Perform systematic, safety‑preserving refactoring of code in any language, using dependency analysis, invariant detection, and verification techniques to avoid introducing bugs.
sounio-bootstrap
Work on the self-hosted Sounio compiler bootstrap path: self-hosted/main.sio pipeline modes (--lex, --parse, --check, --ir-dump, --native-compile), frontend corpus gates, and bootstrap binary milestones.