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/dongduong2001/pudo-code-system/integration-testnpx skills add DongDuong2001/pudo-code-system --skill integration-testgit clone --depth 1 https://github.com/DongDuong2001/pudo-code-systemWrote 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/dongduong2001/pudo-code-system/integration-test)<a href="https://agentmods.dev/skills/dongduong2001/pudo-code-system/integration-test"><img src="https://agentmods.dev/badge/skills/dongduong2001/pudo-code-system/integration-test.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.00013 | $0.00156 |
| Opus 5 | $0.00006 | $0.00078 |
| Sonnet 5 | $0.00003 | $0.00031 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
integration-test 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
Integration Test Skill
This skill governs testing the seams and connections between various components of the system.
When to use this skill
- When validating database queries, ORM layers, and transaction logic.
- When ensuring microservices communicate correctly.
- When testing against third-party API contracts.
Guidelines
- Real Infrastructure: Where possible, use real databases (via Docker/Testcontainers) instead of in-memory mocks for accurate behavior replication.
- Clean State: Ensure the database or state is reset before or after each integration test to prevent cross-test pollution.
- Contract Testing: Consider Consumer-Driven Contracts (like Pact) when integrating with external services to catch API changes early.
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 · 19 lines · 13 tokens per session scan A 50b8c9644784
integration-test is a skill published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 29d ago), licensed MIT. It adds 13 tokens to every session and 156 once invoked, about $0.0001 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-31.
Other skills, from other repositories
scale-to-millions
Use this skill whenever the user is designing, reviewing, debugging, or answering interview questions about system/software architecture and scalability — e.g. "scale my app", "how do I handle more traffic", "design a URL shortener / news feed / chat system", "my API is slow under load", "should I shard my database"…
loop-engineering
Use when a repeatable task must become a bounded Trigger -> Execute -> Verify -> State loop, scheduled automation, goal agent, or metric-driven research cycle.
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
anthropic-os
Use when a personal or team operating system needs a bounded redesign using Four-C, closed-loop controls, 70/30 allocation, 3B creativity, experiments, and prediction-error learning.
knowledge-ops
Use when an Obsidian knowledge system needs classification, deduplication, retrieval, synchronization, debt queues, or governed Agent/Wiki promotion.
verify-before-claim
Use when an agent is about to claim completion, correctness, safety, publication, deployment, or any consequential external fact.