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 SecondLifes/delphi-expert --skill dmvcframework-testinggit clone --depth 1 https://github.com/SecondLifes/delphi-expertWrote 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/secondlifes/delphi-expert/dmvcframework-testing)<a href="https://agentmods.dev/skills/secondlifes/delphi-expert/dmvcframework-testing"><img src="https://agentmods.dev/badge/skills/secondlifes/delphi-expert/dmvcframework-testing/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/secondlifes/delphi-expert/dmvcframework-testing"><img src="https://agentmods.dev/badge/skills/secondlifes/delphi-expert/dmvcframework-testing.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.00115 | $0.05941 |
| Opus 5.5 | $0.00046 | $0.02376 |
| Sonnet 5.5 | $0.00023 | $0.01188 |
| Haiku 4.5 | $0.00012 | $0.00594 |
Grade A, and why
dmvcframework-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 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.
This is a copy
89% identical to dmvcframework-testing — 97 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 705 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DMVCFramework Integration Testing Guide
DMVCFramework is available at https://github.com/danieleteti/delphimvcframework
It ships with a full test stack: DUnitX as test runner, an in-process IMVCServer
(Indy Direct) and IMVCRESTClient as the fluent HTTP client. No external server needed —
tests start and stop the server in [SetupFixture]/[TeardownFixture].
TMVCListeneris deprecated as of 3.5 and will be removed in 4.0 (sources/MVCFramework.Server.pas). It is now a thin wrapper overIMVCServer. Do not write new tests against it: build aTMVCEngine, host it withTMVCServerFactory.CreateIndyDirect, and you need no WebModule at all.
Reference test files in the official repository:
unittests/general/TestClient/LiveServerTestU.pasunittests/general/TestClient/ActiveRecordControllerTestU.pasunittests/general/RESTClient/MVCFramework.Tests.RESTClient.pas
REQUIRED REFERENCE — dmvcframework-security. Any endpoint that accepts input from a client (body,
query string, header, cookie, upload, URL) must follow it: access control and IDOR, mass assignment,
SQL injection, XSS, CSRF, path traversal, uploads, security headers, JWT, secrets. Invoke it whenever you
write or review such an endpoint — not only when the user says "security".
When in doubt about an API — verify it, never guess
Never invent an identifier or answer from memory. If you need a signature this skill does not cover, ask the
user for the path to their DelphiMVCFramework checkout and read sources/ (and the matching samples/
project); failing that, read the official repository —
sources ·
samples.
If you still cannot verify it, say so. Where a skill and a sample disagree, the sample wins.
0. STOP — tests go alongside a wizard project
This skill tests an existing DMVCFramework application. It does not create one.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 705 lines · 115 tokens per session scan A d4bff186d577
dmvcframework-testing is a skill published in the GitHub repository SecondLifes/delphi-expert (3 stars, last pushed 1mo ago), licensed MIT. It adds 115 tokens to every session and 5,941 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to dmvcframework-testing, differing in 97 lines, and is treated as a copy.
Other skills, from other repositories
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
testing-patterns
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.