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 irahardianto/awesome-agv --skill testability-patternsgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/testability-patterns)<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/testability-patterns"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/testability-patterns/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/irahardianto/awesome-agv/testability-patterns"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/testability-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 140 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00051 | $0.01689 |
| Opus 5.5 | $0.00020 | $0.00676 |
| Sonnet 5.5 | $0.00010 | $0.00338 |
| Haiku 4.5 | $0.00005 | $0.00169 |
Grade A, and why
testability-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testability Patterns — Implementation Examples
Language-specific examples for the three testability rules defined in @.agents/rules/architectural-pattern.md. Load this skill when you need concrete implementation reference for I/O isolation, pure business logic, or dependency direction in a specific language.
Rule 1: I/O Isolation — Interface + Adapter Pattern
Go
// storage.go — Contract defined in the consumer feature
type Storage interface {
Create(ctx context.Context, task Task) error
GetByID(ctx context.Context, id string) (*Task, error)
}
// storage_pg.go — Production adapter
type PostgresStorage struct{ db *sql.DB }
func (s *PostgresStorage) GetByID(ctx context.Context, id string) (*Task, error) {
// real database query
}
// storage_mock.go — Test adapter
type MockStorage struct {
tasks map[string]*Task
}
func (m *MockStorage) GetByID(ctx context.Context, id string) (*Task, error) {
t, ok := m.tasks[id]
if !ok {
return nil, ErrNotFound
}
return t, nil
}
TypeScript / Vue
// task.api.ts — Contract (service layer)
export interface TaskAPI {
createTask(title: string): Promise<Task>;
getTasks(): Promise<Task[]>;
}
// task.api.backend.ts — Production adapter
export class BackendTaskAPI implements TaskAPI {
async createTask(title: string): Promise<Task> {
return this.http.post('/api/tasks', { title });
}
async getTasks(): Promise<Task[]> {
return this.http.get('/api/tasks');
}
}
// In tests — Test adapter (vi.mock or manual)
export class MockTaskAPI implements TaskAPI {
private tasks: Task[] = [];
async createTask(title: string): Promise<Task> {
const task = { id: crypto.randomUUID(), title };
this.tasks.push(task);
return task;
}
async getTasks(): Promise<Task[]> {
return [...this.tasks];
}
}
Python
# storage.py — Contract via Protocol
from typing import Protocol
class TaskStorage(Protocol):
def get_by_id(self, task_id: str) -> Task: ...
def create(self, task: Task) -> None: ...
# storage_pg.py — Production adapter
class PostgresTaskStorage:
def __init__(self, db: AsyncEngine) -> None:
self._db = db
async def get_by_id(self, task_id: str) -> Task:
# real database query
# In tests — InMemory adapter
class InMemoryTaskStorage:
def __init__(self) -> None:
self._tasks: dict[str, Task] = {}
async def get_by_id(self, task_id: str) -> Task:
if task_id not in self._tasks:
raise TaskNotFoundError(task_id)
return self._tasks[task_id]
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 · 235 lines · 51 tokens per session scan A 5fdec264086e
testability-patterns is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 9d ago), licensed MIT. It adds 51 tokens to every session and 1,689 once invoked, about $0.0002 per session on Opus 5.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
om-module-scaffold
Build a complete standalone business app, module, or CRUD vertical slice using Open Mercato discovery, commands, APIs, ACL/setup, UI, events, search, migrations, and tests. Use for customer management, deal-pipeline changes, CRM lead capture, library/booking/rental systems, "create a module", "add CRUD entity"…
om-troubleshooter
Diagnose and fix standalone Open Mercato bugs across scope, commands, locking, fields, generated registries, UI hydration, cache/search, bootstraps, queues, and providers. Use for "fix bug", "why does this fail", "regression", "debug", "napraw błąd", or a failing test.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
common-subagent-driven-development
Execute multi-task implementation plans by dispatching a fresh implementer subagent per task with independent review gates. Use when implementing plans, executing multi-task PRs, or transitioning from planning to implementation.
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.