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 tamnguyendinh/Anvien --skill nguyen_ly_test_file_tach_bietgit clone --depth 1 https://github.com/tamnguyendinh/AnvienWrote 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/tamnguyendinh/anvien/nguyen_ly_test_file_tach_biet)<a href="https://agentmods.dev/skills/tamnguyendinh/anvien/nguyen_ly_test_file_tach_biet"><img src="https://agentmods.dev/badge/skills/tamnguyendinh/anvien/nguyen_ly_test_file_tach_biet/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/tamnguyendinh/anvien/nguyen_ly_test_file_tach_biet"><img src="https://agentmods.dev/badge/skills/tamnguyendinh/anvien/nguyen_ly_test_file_tach_biet.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.00105 | $0.02284 |
| Opus 5.5 | $0.00042 | $0.00914 |
| Sonnet 5.5 | $0.00021 | $0.00457 |
| Haiku 4.5 | $0.00011 | $0.00228 |
Grade A, and why
nguyen-ly-test-file-tach-biet 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nguyên Lý Thư Mục Kiểm Thử Tách Biệt (electron/test/) cho tầng Desktop/Frontend.
1. Tổng Quan Kiến Trúc
• Nguyên lý cốt lõi: Tách bạch 100% mối quan tâm (Separation of Concerns). o Cây thư mục mã nguồn (renderer/, main/, preload/) chỉ chứa mã nguồn phục vụ kinh doanh và vận hành của app. o Toàn bộ mã kiểm thử nội bộ, mock data, fixture giả lập được gom gọn vào thư mục electron/test/. o Kiểm thử giao diện và hành vi toàn diện người dùng (E2E) giữ nguyên độc lập tại playwright/ ở root.
2. Bản Đồ Cây Thư Mục Chuẩn Hóa (Directory Tree)
G:\<root_repo>\
├── playwright/ <-- [TẦNG 1] E2E & Visual Regression (Chạy app Electron thật)
│ ├── app/
│ │ ├── pos-checkout.spec.ts
│ │ └── table-management.spec.ts
│ └── shared/
│
├── electron/ <-- Thư mục gốc Desktop App
│ ├── main/ <-- [CODE SẢN PHẨM] Node.js Main Process (Window, IPC, Tray, HW)
│ │ ├── index.ts
│ │ ├── ipc-handlers.ts
│ │ └── printer-manager.ts
│ │
│ ├── preload/ <-- [CODE SẢN PHẨM] ContextBridge an toàn giữa Main và UI
│ │ └── index.ts
│ │
│ ├── renderer/ <-- [CODE SẢN PHẨM] React UI (Giao diện người dùng)
│ │ ├── src/
│ │ │ ├── components/
│ │ │ │ ├── TableCard.tsx
│ │ │ │ └── OrderSummary.tsx
│ │ │ ├── stores/
│ │ │ │ └── useCartStore.ts
│ │ │ ├── utils/
│ │ │ │ └── currency-formatter.ts
│ │ │ ├── App.tsx
│ │ │ └── main.tsx
│ │
│ └── test/ <-- [TẦNG 2] TOÀN BỘ KIỂM THỬ NỘI BỘ (TÁCH BIỆT 100%)
│ ├── fixtures/ <-- Dữ liệu mẫu (mock menus, orders, tables, settings)
│ │ ├── mock-menu-items.json
│ │ └── mock-table-states.json
│ │
│ ├── test_setup.ts <-- Cấu hình môi trường test (DOM ảo, mock IPC bridge)
│ │
│ ├── unit/ <-- Test hàm thuần túy, logic tính toán, store state
│ │ ├── currency-formatter.test.ts
│ │ └── useCartStore.test.ts
│ │
│ ├── components/ <-- Test render React component (soi chiếu với renderer/components)
│ │ ├── TableCard.test.tsx
│ │ └── OrderSummary.test.tsx
│ │
│ └── main/ <-- Test logic của Node.js Main process
│ ├── ipc-handlers.test.ts
│ └── printer-manager.test.ts
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 · 165 lines · 105 tokens per session scan A cc7d6a3adfc0
nguyen-ly-test-file-tach-biet is a skill published in the GitHub repository tamnguyendinh/Anvien (10 stars, last pushed 2d ago), licensed MIT. It adds 105 tokens to every session and 2,284 once invoked, about $0.0004 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-10-06.
Other skills, from other repositories
source-command-swarm-testing
Migrated source command swarm-testing.
source-command-sparc-tester
Migrated source command sparc-tester.
stage-9-deployment
You are a QA gate. All tests must pass. No exceptions. You do not interpret failures — you report them and block. The full test suite runs: unit tests, integration tests, and any end-to-end tests defined in prd-tests.md. A single failure blocks progression.
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.