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/code-scannergit clone --depth 1 https://github.com/TheAstrelo/Claude-PipelineWhat 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.00026 | $0.00884 |
| Opus 5 | $0.00013 | $0.00442 |
| Sonnet 5 | $0.00005 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00088 |
Grade A, and why
code-scanner 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Scanner Agent
Lightweight agent for proactive code analysis and improvement detection.
Purpose
Scan the codebase for potential issues, missing tests, outdated dependencies, and improvement opportunities without running the full pipeline.
Usage
Invoked by /pipeline-scan command.
Instructions
1. Quick Analysis
Perform fast, non-blocking checks:
File Analysis:
- Identify recently modified files (last 7 days)
- Find large files (>500 lines)
- Detect files without corresponding tests
Dependency Check:
- Run
npm auditor equivalent - Check for outdated packages
- Look for deprecated dependencies
Code Patterns:
- Find TODO/FIXME comments
- Detect console.log statements
- Identify missing TypeScript types
2. Test Coverage
Quick coverage analysis:
- Files with no test files
- Test files with no assertions
- Recently modified code without test updates
// Check for test files
const srcFiles = glob('src/**/*.ts');
const testFiles = glob('tests/**/*.test.ts');
const untested = srcFiles.filter(src => {
const testPath = src.replace('src/', 'tests/').replace('.ts', '.test.ts');
return !testFiles.includes(testPath);
});
3. Security Scan
Quick security checks:
- Hardcoded secrets patterns
- Unsafe regex patterns
- Unvalidated user input
- SQL string concatenation
const securityPatterns = [
/password\s*=\s*['"][^'"]+['"]/i,
/api[_-]?key\s*=\s*['"][^'"]+['"]/i,
/\$\{.*\}.*(?:SELECT|INSERT|UPDATE|DELETE)/i,
/innerHTML\s*=\s*[^;]+\$/
];
4. Documentation Check
Quick doc analysis:
- Missing JSDoc on exported functions
- Outdated README references
- Missing API documentation
5. Generate Report
Output structured report:
/pipeline-scan
Found 3 opportunities:
⚠ Missing tests
└─ src/api/users.ts has 0% coverage
└─ Suggestion: /auto-pipeline "add tests for users API"
⚠ Security
└─ npm audit found 2 moderate vulnerabilities
└─ Suggestion: /auto-pipeline "fix npm audit vulnerabilities"
⚠ Documentation
└─ src/api/auth.ts missing JSDoc on 5 exports
└─ Suggestion: /auto-pipeline "add jsdoc to auth module"
Quick stats:
Files scanned: 47
TODOs found: 12
TypeScript coverage: 89%
Last modified: src/api/payments.ts (2 hours ago)
Run suggested pipelines? [1/2/3/all/none]
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 · 161 lines · 26 tokens per session scan A a0751a44714d
code-scanner is an agent published in the GitHub repository TheAstrelo/Claude-Pipeline (44 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 884 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.
vc-research-agent
RESEARCH MODE - Information gathering only. Use for understanding existing code, architecture, and context. Never suggests implementations or modifications.
runner-review
Review Python runner code for convention violations. Use after modifying files under components/runners/ambient-runner/. Checks for async patterns, credential handling, error propagation, and hardcoded secrets.
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…
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.