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.
git clone --depth 1 https://github.com/jaycewalzer1/SilverKey-Inc.Wrote 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/rules/jaycewalzer1/silverkey-inc./qa-test-accounts)<a href="https://agentmods.dev/rules/jaycewalzer1/silverkey-inc./qa-test-accounts"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./qa-test-accounts/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/rules/jaycewalzer1/silverkey-inc./qa-test-accounts"><img src="https://agentmods.dev/badge/rules/jaycewalzer1/silverkey-inc./qa-test-accounts.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.00000 | $0.01344 |
| Opus 5.5 | $0.00000 | $0.00538 |
| Sonnet 5.5 | $0.00000 | $0.00269 |
| Haiku 4.5 | $0.00000 | $0.00134 |
Grade A, and why
qa-test-accounts scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "${API_BASE}/api/v1/auth/login" \ How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA test accounts (SIL-145) — agent sign-in and flow probing
Prerequisite
SIL-145 / SIL-126 step 1 must be complete: committed credentials at:
documentation/runbooks/qa/test-accounts.json
- Do not guess emails, passwords, or OTP inboxes.
- If the file is missing,
sharedPasswordis empty/placeholder, or accounts are not provisioned (login fails /needs_verification), stop and point to provision-test-accounts.md. - Schema template: test-accounts.example.json
Credential discovery
- Read
documentation/runbooks/qa/test-accounts.jsonat task start. - Use
env+baseUrls.web/baseUrls.apifor the active environment (default in file: production). - Password:
sharedPassword(ortest-accounts.local.jsonif team moved password out of git). - Map flow → role(s) using
accounts[]entries:buyer|seller|agent|brokerage|integration_partner.
role |
workspace (expected) |
Primary surfaces to exercise |
|---|---|---|
buyer |
buyer |
Search /search, Library /library, Dashboard /dashboard, buyer messaging |
seller |
seller |
Seller shell routes under /dashboard (seller workspace) |
agent |
agent |
Client hub /dashboard/client/:id, agent messaging, ClientSelector, client checklists |
brokerage |
brokerage |
Brokerage dashboard (activeWorkspace === "brokerage"), roster with linked agents |
integration_partner |
integration_partner |
Partner/integration surfaces once role is granted |
Workspace behavior: documentation/workspace-first-architecture.md. After login, useActiveWorkspace() should match the account’s workspace; do not use SIL-123 dev persona switcher for cross-role QA — use separate logins per role.
API base URL fallback
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 · 115 lines · 0 tokens per session scan A e1a85435d420
qa-test-accounts is a cursor rule published in the GitHub repository jaycewalzer1/SilverKey-Inc. (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,344 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other cursor rules, from other repositories
puppeteer
This guide provides opinionated, actionable best practices for writing robust, performant, and maintainable Puppeteer scripts for web scraping, automation, and testing. It emphasizes modern patterns like page.locator() and efficient resource management.
testing
Shared Svelte testing guidance.
safari-automation
Patterns and best practices for automating Safari browser interactions for web UI automation and testing.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
qa-script-executor
QA Script Executor - Executes natural language test scripts using Chrome DevTools MCP and enhances them with technical hints.
mind2web-eval
Mind2Web offline grounding eval — strict bbox, one query, no eval oracle.