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/shennawardana23/skillme/php-codeigniter-tddnpx skills add shennawardana23/skillme --skill php-codeigniter-tddgit clone --depth 1 https://github.com/shennawardana23/skillmeWrote 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/shennawardana23/skillme/php-codeigniter-tdd)<a href="https://agentmods.dev/skills/shennawardana23/skillme/php-codeigniter-tdd"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/php-codeigniter-tdd.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.1 | $0.00087 | $0.01892 |
| Opus 5 | $0.00044 | $0.00946 |
| Sonnet 5 | $0.00017 | $0.00378 |
| Haiku 4.5 | $0.00009 | $0.00189 |
Grade A, and why
php-codeigniter-tdd 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 3d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHP CodeIgniter TDD
Red-green-refactor for CodeIgniter 4 (CI4), with the framework-specific parts:
which trait wires up the database per test, why CI4 insists on a separate
tests database group, and how to assert against a full HTTP request/response
cycle instead of calling a controller method directly.
For the generic RED-GREEN-REFACTOR cycle, see skills/test-driven-development/.
This skill covers what's specific to CI4 on top of that cycle.
Base class and traits
Every CI4 test extends CodeIgniter\Test\CIUnitTestCase. Add
CodeIgniter\Test\DatabaseTestTrait only when the test actually touches the
database — it adds real per-test cost (migration/refresh/seed), so a pure
unit test (a value object, a calculator) should not use it.
use CodeIgniter\Test\CIUnitTestCase;
use CodeIgniter\Test\DatabaseTestTrait;
final class ReservationModelTest extends CIUnitTestCase
{
use DatabaseTestTrait;
protected $refresh = true;
protected $seed = 'ReservationSeeder';
public function testCreateRejectsCheckOutBeforeCheckIn(): void
{
$model = new \App\Models\ReservationModel();
$result = $model->insert([
'guest_id' => 1,
'check_in' => '2026-06-10',
'check_out' => '2026-06-05',
]);
$this->assertFalse($result);
$this->assertArrayHasKey('check_out', $model->errors());
}
}
The tests database group — not optional, not decorative
DatabaseTestTrait requires a dedicated tests connection group defined in
app/Config/Database.php, separate from default. Per the CI4 user guide,
this exists specifically so database tests never touch "your other data" —
the trait's $migrate/$refresh/$seed behavior runs migrations, seeds, and
(with $refresh = true) rolls back or re-migrates the schema, against
whichever connection the tests group actually points to.
// app/Config/Database.php
public array $tests = [
'DSN' => '',
'hostname' => 'localhost',
'database' => 'app_test', // a real, separate database
'username' => 'root',
'password' => '',
'DBDriver' => 'MySQLi',
'port' => 3306,
];
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.
- 3d ago First seen · 179 lines · 87 tokens per session scan A 5381114c2e56
php-codeigniter-tdd is a skill published in the GitHub repository shennawardana23/skillme (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 87 tokens to every session and 1,892 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-09-03.
Other skills, from other repositories
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
tdd
Enforces strict Test-Driven Development with RED-GREEN-REFACTOR cycles. Writes one failing test at a time, implements minimal code to pass, then refactors. Delegates to the test-provenance-guard skill during REFACTOR to detect tests-by-construction (static + mutation checks). Pairs with the code-quality skill: invokes…
issue-driven-development
Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification.
tdd-full-coverage
Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement.
test-driven-development
Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
test-driven-development
在实现任何功能或修复 bug 时使用,在编写实现代码之前.