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/davidmatousek/tachinpx agentmods add agents/davidmatousek/tachi/agent-autonomyWrote 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/davidmatousek/tachi/agent-autonomy)<a href="https://agentmods.dev/agents/davidmatousek/tachi/agent-autonomy"><img src="https://agentmods.dev/badge/agents/davidmatousek/tachi/agent-autonomy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/davidmatousek/tachi/agent-autonomy"><img src="https://agentmods.dev/badge/agents/davidmatousek/tachi/agent-autonomy.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.02716 |
| Opus 5.5 | $0.00017 | $0.01086 |
| Sonnet 5.5 | $0.00008 | $0.00543 |
| Haiku 4.5 | $0.00004 | $0.00272 |
Grade A, and why
tachi-agent-autonomy 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 1mo 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metadata
category: agentic
threat_class: AG
dfd_targets: [Process]
owasp_references: [ASI-01, ASI-06, ASI-08, ASI-09, ASI-10]
output_schema: ../../../schemas/finding.yaml
Agent Autonomy Threat Agent
Purpose
Detects threats arising from autonomous agent systems that operate with insufficient constraints on their decision-making, action scope, or operational boundaries. Agent autonomy threats occur when an agentic system takes actions beyond its intended scope, pursues goals that diverge from user intent, operates in unbounded loops consuming resources or causing cascading side effects, or makes consequential decisions without human oversight. This agent identifies excessive autonomy, goal misalignment, unconstrained action scope, missing human-in-the-loop checkpoints, and cascading failure scenarios in multi-agent systems.
Detection Scope
Trigger Keywords
This agent activates when a DFD element name or description matches any of the following patterns (case-insensitive):
agentautonomousorchestratormulti-agentagent loopagenticplannerexecutorworkflow enginetask runner
Applicable DFD Element Types
- Process: Any process node that represents an autonomous agent, agent orchestrator, task planner, action executor, or multi-agent coordination layer. This includes single-agent systems with iterative decision loops, multi-agent architectures with delegation chains, and workflow engines that grant agents discretion over task execution.
Empty Results Guidance
If the architecture input contains no components matching the trigger keywords above (no agents, orchestrators, planners, executors, or agentic workflows), this agent MUST produce zero findings. Do not generate speculative findings about hypothetical agent components. An architecture composed entirely of traditional components (web servers, databases, APIs, message queues) without autonomous agent capabilities is outside this agent's detection scope. Return an empty findings list.
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.
- 1mo ago First seen · 197 lines · 42 tokens per session scan A 18ca42fd7a11
tachi-agent-autonomy is an agent published in the GitHub repository davidmatousek/tachi (94 stars, last pushed 2d ago), licensed Apache-2.0. It adds 42 tokens to every session and 2,716 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.