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 tahirraufkeeyu/software-development-agent-stack--sdas --skill full-regressiongit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/full-regression)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/full-regression"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/full-regression.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.1 | $0.00055 | $0.02444 |
| Opus 5 | $0.00028 | $0.01222 |
| Sonnet 5 | $0.00011 | $0.00489 |
| Haiku 4.5 | $0.00006 | $0.00244 |
Grade A, and why
full-regression 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 8d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Invoke this orchestrator when any of the following hold:
- A release candidate (tag, RC branch, or staging deploy) needs sign-off before promotion to production.
- A risk-significant change landed (schema migration, auth rework, checkout flow, pricing, payments) and the team wants a full sweep rather than targeted tests.
- The release train runs on a schedule (weekly, biweekly) and this is the pre-cut checkpoint.
- A previous release was rolled back and leadership wants a reproducible quality gate.
Do not use for per-commit CI — this is heavier than PR-level gates. For a PR check, invoke the individual skills directly.
Chained skills
This orchestrator composes six existing QA skills in a fixed order. Each downstream skill consumes the artifacts of the previous one. Failure in any step does not abort the run — results are collected and summarized so the reviewer sees the full picture.
test-data-generator— produces a deterministic fixture set so every test run is reproducible.api-test-generator— Schemathesis-driven property tests against the OpenAPI spec; fastest feedback first.e2e-test-generator— Playwright or Cypress tests running against the staging URL.performance-test— Lighthouse + Chrome DevTools traces for Core Web Vitals on the top 5 most-visited pages.accessibility-audit— axe-core + manual-checklist pass for WCAG 2.1 AA on the same pages as performance.bug-report— invoked once per FAIL-severity finding; drafts ticket-ready bug reports with repro steps, screenshots, and logs.
Inputs
release— release identifier (e.g.2026.04.2,v3.14.0). Used in filenames and the report header.staging_url— base URL for E2E, performance, and a11y (e.g.https://staging.example.com).openapi_spec_path— local path or URL to the OpenAPI document Schemathesis will fuzz.top_pages— array of 5 path strings for perf + a11y (e.g.["/", "/catalog", "/product/sample", "/cart", "/checkout"]). Source from analytics; fall back to ICP-critical flows if analytics is unavailable.thresholds(optional) — overrides for pass/fail gates. Defaults: LCP <= 2.5s, INP <= 200ms, CLS <= 0.1, 0 WCAG AA violations, 0 API 5xx on valid inputs.
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.
- 8d ago First seen · 153 lines · 55 tokens per session scan A af13548c7b21
full-regression is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 2,444 once invoked, about $0.0003 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-30.
Other skills, from other repositories
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.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
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…