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-report-generationnpx skills add layer1labs/specsmith --skill testing-report-generationgit 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.00014 | $0.00366 |
| Opus 5 | $0.00007 | $0.00183 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
testing-report-generation 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 Report Generation
This skill enables specsmith projects to automatically generate test reports while maintaining governance compliance.
Requirements Covered
- REQ-105: Testing Report Generation
- Allows specsmith projects to automatically generate test reports with human approval
Integration Capabilities
Report Features
- Automated test report generation
- Multiple report formats (HTML, JSON, XML)
- Coverage reporting and analytics
- Test summary and detailed results
- Historical report comparison
- Integration with CI/CD pipelines
Governance Requirements
- Human approval required for report generation
- Configuration management with governance controls
- Approval-based report formats
- Audit logging of report generation activities
Usage Examples
# Initialize report generation
specsmith skill install testing-report-generation
# Generate test report
specsmith test report generate --format html --suite e2e-tests
# Configure report settings
specsmith test report configure --format html --include-coverage true --retention-days 60
Configuration
The skill requires the following configuration in scaffold.yml:
reporting:
format: "html"
include_coverage: true
include_screenshots: false
retention_days: 60
generate_on_success: true
generate_on_failure: true
Security Considerations
- All report generation requires human approval
- Report content must be properly secured
- Access controls for reports must be enforced
- Sensitive data in reports must be handled appropriately
Compliance Requirements
- Follow security best practices for report generation
- Maintain audit logs of all report generation activities
- Ensure proper retention and deletion policies
- Enforce approval-based report generation
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 · 14 tokens per session scan A e938b05f34df
testing-report-generation is a skill published in the GitHub repository layer1labs/specsmith (7 stars, last pushed 29d ago), licensed MIT. It adds 14 tokens to every session and 366 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
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.
pr-review
Autonomous local code review. Reviews either an open PR's diff (via gh) or the local working diff against a base branch (--local, auto-selected when no PR exists yet), spawns a dedicated review subagent with universal + stack-specific severity criteria, posts the review as a comment on the PR (audit trail; skipped in…
responsive-audit
Responsive audit: test pages at 375/768/1024px breakpoints via Playwright. Checks overflow, tap targets, sidebar collapse, text reflow, WCAG 1.4.4 zoom.
security-audit
Security audit: auth/authz on API routes, input validation, row-level access control (RLS in Postgres, ORM scopes or app-level guards elsewhere), response shape review, secret exposure, HTTP headers. Native mode checks entitlements and Keychain. MCP-aware (v1.20+): when mcp-nvd server is wired, Step 3c queries live…