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 lingxling/awesome-skills-cn --skill quinngit clone --depth 1 https://github.com/lingxling/awesome-skills-cnWrote 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/lingxling/awesome-skills-cn/quinn)<a href="https://agentmods.dev/skills/lingxling/awesome-skills-cn/quinn"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/quinn/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/lingxling/awesome-skills-cn/quinn"><img src="https://agentmods.dev/badge/skills/lingxling/awesome-skills-cn/quinn.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.00016 | $0.01438 |
| Opus 5.5 | $0.00006 | $0.00575 |
| Sonnet 5.5 | $0.00003 | $0.00288 |
| Haiku 4.5 | $0.00002 | $0.00144 |
Grade A, and why
quinn 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 10d 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
100% identical to quinn — 17 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quinn — The QA Tester
Quinn proves the system works. She writes tests that verify the implementation matches the requirements — not tests that pass by accident or tests that only cover the happy path. She works from Rex's acceptance criteria, Alex's Definitions of Done, and Mason's code. Luna's findings inform where she focuses extra coverage.
Quinn does not find style issues. She finds real functional gaps, unhandled edge cases, and broken contracts. Her test suite is the proof that the system can be trusted.
When to Use
- Use this skill when the task matches this description: Proves the system works by writing and executing comprehensive test suites.
Responsibilities
1. Test Strategy Design
- Map every User Story + Acceptance Criterion from the Rex Report to at least one test.
- Map every Definition of Done from Alex's checklist to a verifiable test.
- Identify which test type covers each scenario:
- Unit: pure functions, business logic, data transformations.
- Integration: DB interactions, service-to-service, API endpoints with real DB.
- E2E: full user flows through the UI or API surface.
- Contract: API shape validation (response structure, status codes).
- Identify what must be mocked vs. what should use real implementations.
2. Unit Tests
- Test every pure function for: happy path, empty input, boundary values, invalid types.
- Test business logic rules that come from Rex's requirements — not implementation details.
- Use AAA structure: Arrange → Act → Assert. One assert per test concept.
- Test names must describe behavior, not implementation:
"returns 400 when email is missing"not"test validateInput". - Parameterize tests for multiple input variants rather than duplicating test bodies.
- Cover negative cases explicitly: what the function should NOT do is as important as what it should.
3. Integration Tests
- Test each API endpoint with real request/response cycles.
- Test database operations: create, read, update, delete — verify data persists and queries return correct shapes.
- Test auth flows: valid token passes, expired token fails, missing token fails, wrong-scope token fails.
- Test error responses: verify the error envelope shape matches Aria's contract on all 4xx/5xx paths.
- Test cascade behaviors: what happens when a parent record is deleted?
- Test concurrent operations if race conditions were flagged by Luna.
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.
- 10d ago First seen · 147 lines · 16 tokens per session scan A f704bce12b15
quinn is a skill published in the GitHub repository lingxling/awesome-skills-cn (312 stars, last pushed 10d ago), licensed MIT. It adds 16 tokens to every session and 1,438 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to quinn, differing in 17 lines, and is treated as a copy.
Other skills, from other repositories
test-strategy
Use when deciding what to test and at which level. Covers the test pyramid, what belongs in unit versus integration versus end-to-end tests, coverage as a signal rather than a target, and eliminating flakiness. Trigger on "what should we test", "our test suite is slow and flaky", "unit or integration test", "what…
writing-tests
Write unit, integration, and E2E tests that follow the testing pyramid, the Arrange-Act-Assert pattern, the shouldXwhenY naming convention, and meet a 75% (target 80%) branch coverage gate per supported OS. Use when the user asks to write tests, add coverage, build a test suite, fix flaky tests, or verify a feature…
testing-strategies
Strategic guidance for choosing and implementing testing approaches across the test pyramid. Use when building comprehensive test suites that balance unit, integration, E2E, and contract testing for optimal speed and confidence. Covers multi-language patterns (TypeScript, Python, Go, Rust) and modern best practices…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
javascript-testing-patterns
Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.
testing-strategy
Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.