Borrowing it
Nothing to install: this file belongs to ourines/codes. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ourines/codes/main/.claude/skills/codes-e2e-test/SKILL.mdgit clone --depth 1 https://github.com/ourines/codesWrote 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/ourines/codes/codes-e2e-test)<a href="https://agentmods.dev/skills/ourines/codes/codes-e2e-test"><img src="https://agentmods.dev/badge/skills/ourines/codes/codes-e2e-test/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/ourines/codes/codes-e2e-test"><img src="https://agentmods.dev/badge/skills/ourines/codes/codes-e2e-test.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.00047 | $0.05831 |
| Opus 5.5 | $0.00019 | $0.02332 |
| Sonnet 5.5 | $0.00009 | $0.01166 |
| Haiku 4.5 | $0.00005 | $0.00583 |
Grade A, and why
codes-e2e-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 2mo 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 — 927 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codes E2E Test Suite
codes CLI 全功能端到端验证。每个模块遵循 Setup → Execute → Assert → Cleanup 模式。
Test Modes
| Mode | Purpose |
|---|---|
--all |
Run all modules (1-10) |
--module <name> |
Run single module: project, profile, config, remote, agent, workflow, mcp, cli, http, notify |
--issue <number> |
Run issue-specific verification (Module 11) |
--quick |
Modules 1, 3, 8 only (Project + Config + CLI basics) |
Prerequisites
cd /Users/ourines/Projects/codes
go build -o /tmp/codes-e2e-bin ./cmd/codes
Verify: /tmp/codes-e2e-bin version should output version info.
Set test binary alias for all subsequent steps:
CODES="/tmp/codes-e2e-bin"
Module 1: Project CRUD
TEST_DIR=$(mktemp -d /tmp/codes-e2e-project-XXXXXX)
mkdir -p "$TEST_DIR"
$CODES project add e2e-test-proj "$TEST_DIR"
Assert: Output contains success message. Exit code 0.
$CODES project list
Assert: Output contains e2e-test-proj and the path $TEST_DIR.
$CODES project list --json
Assert: Valid JSON output. Contains key e2e-test-proj.
$CODES --json project list 2>/dev/null | grep -q "e2e-test-proj"
Assert: Project info is retrievable.
$CODES project remove e2e-test-proj
Assert: Exit code 0. $CODES project list no longer shows e2e-test-proj.
rm -rf "$TEST_DIR"
Module 2: Profile CRUD
Note: profile add and profile select are interactive (TTY) commands. This module tests them
via direct config file manipulation as a fallback, or requires manual interaction in a TTY session.
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.
- 2mo ago First seen · 927 lines · 47 tokens per session scan E fc03612a7cfa
codes-e2e-test is a skill published in the GitHub repository ourines/codes (11 stars, last pushed 8mo ago), licensed MIT. It adds 47 tokens to every session and 5,831 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-08-30.
Other skills, from other repositories
apifox-test-scenario
A guide for building and managing Apifox test scenarios, which are ordered workflows that check how several API calls and other actions work together.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
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…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.