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 agentmods add skills/paruff/ufawkesai/full-stacknpx skills add paruff/uFawkesAI --skill full-stackgit clone --depth 1 https://github.com/paruff/uFawkesAIWhat 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 | $0.00042 | $0.00505 |
| Opus 5 | $0.00021 | $0.00253 |
| Sonnet 5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
full-stack-integration 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 3d 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.
What it actually says
Skill: Full Stack Integration Testing
Load trigger:
"load full-stack-integration skill"> DORA: Cap 4 (CI/CD Automation) Token cost: Low
Purpose
Validate the entire OBS + PIPE + GitOps + K8s flow end-to-end.
Responsibilities
- Run full pipeline
- Validate GitOps update
- Validate reconciliation
- Validate deployment
- Validate smoke tests
Inputs
- Full system
Outputs
full-integration-report.jsoncluster-state.json
Sub-Skills
| Skill | Purpose |
|---|---|
full-stack/cluster-state |
Validate cluster state matches Git |
full-stack/smoke-tests |
Validate deployed application |
Full Stack Flow
1. Code change triggers PIPE
2. PIPE builds, tests, scans
3. PIPE produces artifacts (image, SBOM, signature)
4. OBS receives artifacts
5. OBS updates GitOps repo
6. Controller reconciles
7. K8s deploys
8. Smoke tests validate
Validation Rules
- Full pipeline completes
- GitOps update valid
- Reconciliation successful
- Deployment healthy
- Smoke tests pass
Output Format
{
"skill": "full-stack-integration",
"status": "pass | fail",
"pipeline": { "status": "pass", "time_s": 300 },
"gitops_update": { "status": "pass", "commit": "abc123" },
"reconciliation": { "status": "pass", "time_s": 60 },
"deployment": { "status": "pass", "replicas": 3 },
"smoke_tests": { "status": "pass", "tests": 10 }
}
Success Criteria
- End-to-end correctness
- Healthy deployment
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 83 lines · 42 tokens per session scan A 4f914a559beb
full-stack-integration is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 10d ago), licensed MIT. It adds 42 tokens to every session and 505 once invoked, about $0.0002 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-31.
Other skills, from other repositories
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.
qa/e2e-playwright
Playwright E2E 测试完整方法论，涵盖项目初始化、Page Object Model、认证复用、API Mock、视觉回归、多浏览器测试、CI 集成和调试技巧.
exa-search
Use Exa MCP for current web, code/docs, company, people, and page-fetch research. Prefer current hosted tool schemas and note deprecated tools.
ontoly-software-graph
Use Ontoly's deterministic Software Graph and MCP capabilities for repository architecture, request tracing, dependency analysis, configuration lookup, and impact analysis before falling back to source search.
helpers
Plain utility function conventions for the Playwright scaffold — app-specific helpers in helpers/{area}/ (authentication bootstrap, storage-state creation, data seeding) and generic utilities in helpers/util/ (date formatting, string manipulation, parsing). Use when adding a reusable function that does NOT need the…
test-standards
Spec file conventions for the Playwright scaffold — imports from test-options.ts, test file structure (describe / beforeEach / test / test.step), single-tag rule, functional vs E2E vs API vs setup test types, data-driven test loops against TS static data, web-first assertions, destructive-test cleanup, and test…