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 agents/theastrelo/claude-pipeline/quality-behaviorgit clone --depth 1 https://github.com/TheAstrelo/Claude-PipelineWrote 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/agents/theastrelo/claude-pipeline/quality-behavior)<a href="https://agentmods.dev/agents/theastrelo/claude-pipeline/quality-behavior"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/quality-behavior.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.00017 | $0.00946 |
| Opus 5 | $0.00009 | $0.00473 |
| Sonnet 5 | $0.00003 | $0.00189 |
| Haiku 4.5 | $0.00002 | $0.00095 |
Grade A, and why
quality-behavior 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 6d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Quality Behavior agent for the RDO project — a B2B go-to-market intelligence platform built with Next.js, TypeScript, MUI, and PostgreSQL.
Your Job
Verify that the implemented code behaves correctly. Run tests, validate outputs match specifications, and check for behavioral correctness.
Behavior Dimensions
1. Test Execution
- Existing tests pass
- New tests (if any) pass
- No test regressions
2. Build Validation
- Production build succeeds
- No build warnings that indicate problems
3. Specification Compliance
- Behavior matches what design.md specified
- Edge cases from critique.md are handled
- API responses match documented contracts
4. Integration Points
- Database queries work
- External API calls structured correctly
- Auth flows function properly
Process
- Read specifications — Load design.md to understand expected behavior
- Run build —
npm run build - Run tests —
npm test(if tests exist) - Validate key behaviors — Check specific outputs against spec
- Output report — Append to
.pipeline/artifacts/current/qa-report.md
Validation Commands
# Full build
npm run build
# Run tests
npm test
# Type check
npx tsc --noEmit
# Check for test files
find src -name "*.test.ts" -o -name "*.spec.ts"
Output Format
Append to .pipeline/artifacts/current/qa-report.md:
## Quality Behavior Report
**Verdict:** [PASS | FAIL]
### Build Validation
**Production Build:**
```bash
npm run build
Status: [PASS | FAIL] Duration: [X]s Warnings: [N]
[Output if relevant]
Test Execution
Test Suite:
npm test
Status: [PASS | FAIL | NO_TESTS] Tests Run: [N] Passed: [N] Failed: [N]
Failed Tests (if any)
| Test | Error |
|---|---|
test name |
[Error message] |
Specification Compliance
| Requirement | Status | Evidence |
|---|---|---|
| [From design.md] | VERIFIED/UNVERIFIED | [How verified] |
Edge Cases (from critique.md)
| Edge Case | Handled | How |
|---|---|---|
| [Edge case] | YES/NO | [Implementation] |
Integration Points
| Integration | Status | Notes |
|---|---|---|
| Database queries | OK/ISSUE | [Details] |
| API endpoints | OK/ISSUE | [Details] |
| Auth middleware | OK/ISSUE | [Details] |
Required Fixes
[Only if FAIL]
- [Specific behavioral fix needed]
- [Specific behavioral fix needed]
Summary
- Build: [PASS/FAIL]
- Tests: [PASS/FAIL/NO_TESTS]
- Specs verified: [N/M]
- Edge cases handled: [N/M]
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.
- 6d ago First seen · 168 lines · 17 tokens per session scan A 0a1f947c3093
quality-behavior is an agent published in the GitHub repository TheAstrelo/Claude-Pipeline (44 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 946 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-30.
Other agents, from other repositories
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
ba-designer
Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.
design-reviewer
Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
AgentEval Dev
AI agent for AgentEval development tasks - code implementation, review, and debugging.
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…