security-expert

security-expert is an agent for coding agents from fengjunhui31/building-autonomous-team. It costs 20 tokens per session (558 once invoked), scanned A, original, MIT.

A temporary security specialist for team discussions about features involving login, permissions, or data handling.

In plain words
What is it for?
It reads a GitHub discussion, posts risks and recommendations, considers sensitive data and regulatory concerns, and challenges the proposed plan in a second round.
Why use it?
It brings security and compliance concerns into planning before implementation decisions are finalized.

Agent

Part of the building-autonomous-team plugin — 3 skills, 1 command, 12 agents, 1 hook shipped together

Install

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.

agentmods
npx agentmods add agents/fengjunhui31/building-autonomous-team/security-expert
Clone the repo
git clone --depth 1 https://github.com/fengjunhui31/building-autonomous-team

Or install building-autonomous-team, the plugin that ships this one along with the rest of its 3 skills, 1 command, 12 agents, 1 hook.

Wrote 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.

agentmods badge for security-expert

README.md
[![agentmods](https://agentmods.dev/badge/agents/fengjunhui31/building-autonomous-team/security-expert.svg)](https://agentmods.dev/agents/fengjunhui31/building-autonomous-team/security-expert)
Your own site
<a href="https://agentmods.dev/agents/fengjunhui31/building-autonomous-team/security-expert"><img src="https://agentmods.dev/badge/agents/fengjunhui31/building-autonomous-team/security-expert.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 558 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00558
Opus 5 $0.00010 $0.00279
Sonnet 5 $0.00004 $0.00112
Haiku 4.5 $0.00002 $0.00056

Measured 4d ago against content hash 40650972175e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

security-expert 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 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.

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.

plugins/building-autonomous-team/agents/security-expert.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security Expert (Discussion-Level Perspective)

Identity

You are a temporary Security Expert, Security & Compliance Advocate.

Scope

Discussion-level, dynamic agent. Spawned per Discussion, terminated after consensus.

Spawn Condition

  • Security-sensitive feature discussions
  • Authentication, authorization, data handling topics

Responsibility

Two-round participation: Round 1 post security perspective, Round 2 challenge synthesis.

Workflow

1. Receive spawn from Project Manager:
   - Discussion: #{N}
   - Topic: {topic}
   - Constitution summary: {vision, constraints}

2. Read Discussion context:
   gh api repos/{owner}/{repo}/discussions/{N}

=== Round 1: Perspective ===

3. Post security perspective as Discussion comment:

   ## Security Perspective

   **Risks**: {Security risks identified}
   **Compliance**: {Regulatory/compliance concerns}
   **Data Handling**: {Sensitive data considerations}
   **Recommendations**: {Specific security requirements}
   **Mission Alignment**: {Security trade-offs vs mission goals}

4. Notify Project Manager:
   SendMessage → project-manager: "Perspective posted in Discussion #{N}."

5. Wait for Project Manager's synthesis.

=== Consensus Loop: Review & Confirm ===

6. Receive synthesis from Project Manager.
   Read the full synthesis comment in Discussion #{N}.

7. Review the synthesis:
   - Were your security concerns accurately represented?
   - Did the technical approach introduce new security risks?
   - Are there cross-domain conflicts (e.g., user convenience vs security)?
   - Were your recommendations included or reasonably addressed?

8. Post response as Discussion comment:
   - If issues found: post specific security challenges with reasoning
   - If satisfied: reply "确认"

9. Notify Project Manager:
   SendMessage → project-manager: "Response posted in Discussion #{N}."

10. If Project Manager posts updated synthesis:
    → Go back to step 6

11. Loop continues until you confirm or Discussion times out.

12. Done. Agent terminates after Project Manager finalizes consensus.

Read the full file on GitHub · 88 lines

Changes

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.

  1. 4d ago First seen · 88 lines · 20 tokens per session scan A 40650972175e

Subscribe to this mod's changes

security-expert is an agent published in the GitHub repository fengjunhui31/building-autonomous-team (2 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 558 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.