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/layer1labs/specsmith/testing-cicd-integrationnpx skills add layer1labs/specsmith --skill testing-cicd-integrationgit clone --depth 1 https://github.com/layer1labs/specsmithWhat 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.00020 | $0.00405 |
| Opus 5 | $0.00010 | $0.00202 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
testing-cicd-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 2d 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
Testing Integration with CI/CD
This skill enables specsmith projects to integrate testing frameworks with CI/CD pipelines while maintaining governance compliance.
Requirements Covered
- REQ-106: Testing Integration with CI/CD
- Allows specsmith projects to integrate testing frameworks with CI/CD pipelines with human approval
Integration Capabilities
CI/CD Features
- Pipeline integration for automated testing
- Test execution in CI environments
- Integration with popular CI platforms (GitHub Actions, GitLab CI, Jenkins)
- Test result reporting to CI systems
- Parallel test execution in CI environments
- Environment variable management for tests
Governance Requirements
- Human approval required for CI/CD integration
- Configuration management with governance controls
- Approval-based pipeline setup
- Audit logging of CI/CD activities
Usage Examples
# Initialize CI/CD integration
specsmith skill install testing-cicd-integration
# Configure CI/CD settings
specsmith test cicd configure --platform github-actions --test-parallel true
# Set up CI pipeline
specsmith test cicd setup --pipeline e2e-tests --trigger on-push
Configuration
The skill requires the following configuration in scaffold.yml:
cicd:
platform: github-actions
test_parallel: true
test_timeout: 30000
trigger_on: "on-push"
report_results: true
artifact_storage: "github-artifacts"
Security Considerations
- All CI/CD integrations require human approval
- Pipeline secrets must be properly secured
- Test environment access must be controlled
- Integration with CI systems must be secure
Compliance Requirements
- Follow security best practices for CI/CD integrations
- Maintain audit logs of all CI/CD activities
- Ensure proper pipeline configuration and management
- Enforce approval-based CI/CD setup
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.
- 2d ago First seen · 71 lines · 20 tokens per session scan A a58c2e4345ce
testing-cicd-integration is a skill published in the GitHub repository layer1labs/specsmith (7 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 405 once invoked, about $0.0001 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
infra-audit
Infrastructure and CI/CD security audit - GitHub Actions workflows (pwn-request, secret logging, missing pinning, permissions overreach), Dockerfile (latest tag, USER root, ADD on URL), Kubernetes manifests (runAsNonRoot, privileged containers, hostNetwork), Terraform (IAM wildcards, state in git, module pinning)…
release-patterns
PR creation, CI/CD validation, merge coordination, and release patterns. Use when creating pull requests, running pre-PR validation, checking CI status, coordinating merges, or managing releases. Do NOT use for routine development commits -- see safe-workflow skill instead.
safe-workflow
SAFe development workflow guidance including branch naming conventions, commit message format, rebase-first workflow, and CI validation. Use when starting work on a Linear ticket, preparing commits, creating branches, writing PR descriptions, or asking about contribution guidelines.
arch-audit
Audit Claude Code architecture files against Anthropic docs and release notes, and verify internal ecosystem consistency. Run on demand to maintain compliance, catch new features, and keep the context system clean.
skill-dev
Code quality audit: detect cross-module coupling, N+1 queries, dead exports, antipatterns, over-large components. Cross-checks against refactoring backlog.
accessibility-audit
Unified accessibility audit - axe-core WCAG 2.2 scan, APCA contrast measurement, static a11y checks (aria-label, tabindex, form labels, focus visibility, onClick on non-interactive). Static and live modes.