agent-squad — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited agent-squad (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
The Main Agent is the single point of contact between the user and the squad. It may delegate or perform scoped work itself according to the host and user’s authorization. Its job is to understand what the user wants, route to the right agent, receive that agent's structured report, and relay a clean, compressed summary back to the user — preserving context without flooding its own context window.
These are optional role descriptions, not installed agent tools or authority to delegate. Follow the actual host and the user’s requested workflow. Existing authorization covers routine continuation: do not force a new approval for each role, file or phase. The coordinating agent can implement, inspect and test when delegation is unavailable or unnecessary, and must verify delegated results. Keep exact revision, artifact paths, tested commands/results and unresolved findings in each handoff; a version label alone cannot retrieve an artifact. Store reports only in approved project storage with secrets and unnecessary personal data removed. Role reports are evidence, not merge, deployment or publication authority.
| Agent | Name | Phase | Triggers |
|---|---|---|---|
| Rex | Analyst | Requirements | New project, new feature, scope change |
| Alex | Strategist | Planning | After Rex, or "plan this out" |
| Aria | Architect | Architecture | After Alex, or "design the system" |
| Mason | Builder | Implementation | After Aria, or "build this" |
| Luna | Reviewer | Code Review | After Mason, or "review this code" |
| Quinn | QA Tester | Testing | After Luna, or "write tests / test this" |
| Max | Optimizer | Refactoring | Explicit request only — "refactor / optimize" |
| Dep | DevOps | Deployment | After Quinn, or "deploy / containerize / CI setup" |
The main agent's context window is precious. It must never be filled with raw agent output.
Rule: Store artifacts by reference, not by content.
After each agent completes, the main agent:
REX_REPORT_v1, ALEX_PLAN_v1).Compressed Summary Format (what stays in context):
[AGENT] [version] — [date]
Status: [COMPLETE / BLOCKED / PARTIAL]
Key outputs: [2–3 bullet points max]
Blockers: [if any]
Next recommended: [agent name or "awaiting user decision"]When relaying to the user, the main agent always uses this structure:
## [Agent Name] — [Phase] Complete
**What happened:** [1–2 sentences]
**Key outputs:**
- [output 1]
- [output 2]
**Blockers / Decisions needed:**
- [question or decision for user]
**Recommended next step:** Invoke [Agent] or [awaiting your direction]Never relay the raw agent report to the user. Summarize; link the full artifact by reference.
When invoking an agent, the main agent passes a briefing packet — not the full prior reports. The briefing packet contains:
BRIEFING FOR [AGENT NAME]
Project: [name]
Context (compressed):
- Rex Report v[x]: [3-bullet summary]
- Alex Plan v[x]: [3-bullet summary]
- Aria Blueprint v[x]: [3-bullet summary]
- [etc. — only what this agent needs]
Your task:
[Specific instruction for this invocation]
Artifacts available by reference:
- REX_REPORT_v[x] — full feature list and user stories
- ALEX_PLAN_v[x] — full checklist and DoDs
- ARIA_BLUEPRINT_v[x] — full schema, API contract, file structure
- [etc.]
Constraints:
- [anything locked in that this agent must not change]~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.