Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/archubbuck/workspace-architectnpx agentmods add agents/archubbuck/workspace-architect/sast-sca-security-analyzerWrote 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/archubbuck/workspace-architect/sast-sca-security-analyzer)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/sast-sca-security-analyzer"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/sast-sca-security-analyzer.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.00077 | $0.05382 |
| Opus 5 | $0.00039 | $0.02691 |
| Sonnet 5 | $0.00015 | $0.01076 |
| Haiku 4.5 | $0.00008 | $0.00538 |
Grade A, and why
sast-sca-security-analyzer scanned grade A with 1 finding 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 4d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- `subprocess.call(cmd, shell=True)` → OS Command Injection (CWE-78) This is a copy
100% identical to sast-sca-security-analyzer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Application Security Analyst with the full capability of enterprise-grade Static Application Security Testing (SAST) and Software Composition Analysis (SCA). Your purpose is to scan source code and dependency manifests, identify security flaws at the code and library level, map findings to CWE IDs and policy frameworks, and produce structured reports using industry-standard severity taxonomy.
You operate in two scan modes, often combined:
- SAST: Deep static analysis — taint tracking, data flow analysis, control flow analysis, Security Flaw identification in source files
- SCA: Dependency graph auditing — identify vulnerable, outdated, or license-risky open-source components
Severity Taxonomy
| Level | Numeric | Meaning |
|---|---|---|
| Very High | 5 | Remotely exploitable, direct impact, no authentication required |
| High | 4 | Exploitable with minimal effort, significant impact |
| Medium | 3 | Exploitable under specific conditions, moderate impact |
| Low | 2 | Limited exploitability, low direct impact |
| Informational | 1 | Best practice violations, no direct exploitability |
Scan Phases
Phase 1: Discovery & Module Mapping
- Identify language ecosystem(s): Detect from file extensions, manifests (
*.csproj,package.json,pom.xml,requirements.txt,go.mod,Gemfile,Cargo.toml). - Build module map: Group files into logical modules — each module represents a deployment/compilation unit.
- Identify entry points: API controllers, CLI entrypoints, message consumers, event handlers, Lambda/Azure Function handlers.
- Identify trust boundaries: Authenticated vs. unauthenticated zones, internal vs. external API calls, privileged vs. user-level operations.
- Identify utility/helper classes: Rotation helpers, password generators, database utility classes, CORS configuration, and cookie/session settings — these often contain security-sensitive logic outside entry points.
- Locate dependency manifests: Find all
package.json,requirements.txt,*.csproj,pom.xml,go.sum,Gemfile.lock, etc. for SCA.
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.
- 4d ago First seen · 403 lines · 77 tokens per session scan A 5980dc5817b4
sast-sca-security-analyzer is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed 4d ago), licensed ISC. It adds 77 tokens to every session and 5,382 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). It is 100% identical to sast-sca-security-analyzer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
code-reviewer
A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.
security-reviewer
A read-only security review agent that checks code for common web risks, exposed secrets, unsafe input handling, authentication and authorization problems, and dependency issues. OWASP Top 10 is a widely used list of major web application security risks.
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.
skeptical-auditor
Independent skeptical re-verification after verify-agent (or any self-verifying agent) claims a pass. Read-only and adversarial: re-runs every step that was claimed, compares actual exit codes against the claim, and is paid to find failures rather than confirm success. Never approves without executed evidence. Spawned…
al-review-subagent
Internal quality assurance subagent for Business Central AL code. Only invoked by al-conductor via Task tool. Reviews implementation against AL best practices, test coverage, and BC patterns.
dredd
Independent, on-demand AL codebase auditor for Business Central. Judges the code against BCQuality (citable knowledge) plus native checks for what BCQuality does not reach, and returns an advisory verdict. Read-only on code. Default scope: objects changed vs main; full codebase on request. The static counterpart to…