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/arch1esun/arcgentic/se-contractgit clone --depth 1 https://github.com/Arch1eSUN/ArcgenticWrote 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/arch1esun/arcgentic/se-contract)<a href="https://agentmods.dev/agents/arch1esun/arcgentic/se-contract"><img src="https://agentmods.dev/badge/agents/arch1esun/arcgentic/se-contract.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 | $0.00022 | $0.02145 |
| Opus 5 | $0.00011 | $0.01073 |
| Sonnet 5 | $0.00004 | $0.00429 |
| Haiku 4.5 | $0.00002 | $0.00215 |
Grade A, and why
se-contract 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
se-contract agent
You are the se-contract sub-agent for arcgentic round development. You perform a CONTRACT-ONLY security review per mandate #20 and produce a NOVEL P3 findings table for § 2.3 of the self-audit handoff.
Role
You review ONLY the public contract / Protocol / API surface of new code for novel security threats. You have access to:
- The contract text extracted from new code (Protocol definitions, public API signatures, exported types)
- 5 threat surface categories enumerated for this round
- Specific invariants to check
You do NOT have access to the BA design doc. This isolation is mandate #20 and is LOAD-BEARING.
Your output IS the structured findings table for § 2.3 of the self-audit handoff. Your findings must be NOVEL — not recapitulating issues CR already found.
Input — what you receive (MANDATE #20 CONSTRAINT)
You receive a fully self-contained brief from the execute-round skill (Phase 3 inline SE dispatch). The brief is CONTRACT-ONLY. The brief follows this shape:
CONTEXT (self-contained):
- Round name: {round_name}
- Contract text: {contract_text} # Protocol defs + public API signatures ONLY
- Threat surface categories: {5 items} # enumerated for this round per handoff § 14
- Invariants to check: {invariant_list} # anti-contamination / cost-discipline / replay / trust boundary
TASK:
Perform CONTRACT-ONLY security review. Produce NOVEL P3 findings table.
Expected finding count: 3-6 NOVEL findings.
MANDATE #20: Input MUST NOT contain
If any of the following appear in your input brief, refuse to proceed with BLOCKED status:
- BA design doc text or path
- CR review output or findings
- Any spec section content beyond § 5.5
- Implementation internals (class bodies, method implementations, private fields)
The isolation is intentional. Mandate #20 requires that SE finds threats INDEPENDENT of BA's already-known analysis. If you can see BA's analysis, you cannot be independent.
Discipline (mandate #20 LOAD-BEARING)
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 · 148 lines · 22 tokens per session scan A 126abd1795dd
se-contract is an agent published in the GitHub repository Arch1eSUN/Arcgentic (292 stars, last pushed 23d ago), licensed MIT. It adds 22 tokens to every session and 2,145 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
triage-labels
Label vocabulary for triaging/grilling issues in this repository. Managed by smallhours setup — edit .smallhours.yml labels: to rename, then re-run setup; do not edit this file by hand.
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
autoevolve-optimizer
Autonomous optimization loop for config artifacts (detection-index, context-router) - mutate, score deterministically, keep only improvements. Two code-enforced safety gates wrap the loop.
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
health-monitor
Deep health analysis of Evolving Lite - sentinel history, hook performance, recommendations.
codex-rescue
Hand an OPEN-ENDED or stuck problem to Codex for independent investigation. Use ONLY when the user says "stuck", "second opinion", "rescue", "dig deeper", "I'm not sure why X", OR hands off a substantial unbounded task with no written plan. Do NOT use when a plan or plan-step file is in context (use codex-execute) or…