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 commands/valory-xyz/open-autonomy/autonomy_fetchgit clone --depth 1 https://github.com/valory-xyz/open-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/commands/valory-xyz/open-autonomy/autonomy_fetch)<a href="https://agentmods.dev/commands/valory-xyz/open-autonomy/autonomy_fetch"><img src="https://agentmods.dev/badge/commands/valory-xyz/open-autonomy/autonomy_fetch.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.00000 | $0.01153 |
| Opus 5 | $0.00000 | $0.00576 |
| Sonnet 5 | $0.00000 | $0.00231 |
| Haiku 4.5 | $0.00000 | $0.00115 |
Grade A, and why
autonomy_fetch 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fetch an agent blueprint or AI agent from a registry using its public ID, hash, or token ID.
The autonomy fetch command allows you to download AI agent files from either a local or remote registry.
Usage
autonomy fetch [OPTIONS] PUBLIC_ID_OR_HASH_OR_TOKEN_ID
Options
--remote
: To use a remote registry.
--local
: To use a local registry.
--alias TEXT
: Provide a local alias for the agent blueprint or AI agent.
--agent
: Specify the package type as agent blueprint (default).
--service
: Specify the package type as AI agent.
--help
: Show the help message and exit.
--use-celo
: Use the Celo chain profile to find the token with the given token ID.
--use-base
: Use the Base chain profile to find the token with the given token ID.
--use-optimism
: Use the Optimism chain profile to find the token with the given token ID.
--use-arbitrum-one
: Use the Arbitrum One chain profile to find the token with the given token ID.
--use-gnosis
: Use the Gnosis chain profile to find the token with the given token ID.
--use-polygon
: Use the Polygon chain profile to find the token with the given token ID.
--use-ethereum
: Use the Ethereum chain profile to find the token with the given token ID.
To use these chain profile, you will have to export an environment variable for RPC in <CHAIN_NAME>_CHAIN_RPC format. For example if you want to use ethereum, you will have to export ETHEREUM_CHAIN_RPC.
--use-custom-chain
: Use the custom-chain profile to find the token with the given token ID. This profile requires that you define some parameters and contract addresses as environment variables (see also the {{ autonolas_protocol }} documentation for more information):
- `CUSTOM_CHAIN_RPC` : RPC endpoint for the custom chain.
- `CUSTOM_CHAIN_ID` : chain ID.
- `CUSTOM_COMPONENT_REGISTRY_ADDRESS` : Custom Component Registry contract address.
- `CUSTOM_AGENT_REGISTRY_ADDRESS` : Custom Agent Registry contract address.
- `CUSTOM_REGISTRIES_MANAGER_ADDRESS` : Custom Registries Manager contract address.
- `CUSTOM_SERVICE_MANAGER_ADDRESS` : Custom Service Manager contract address.
- `CUSTOM_SERVICE_REGISTRY_ADDRESS` : Custom Service Registry contract address.
- `CUSTOM_GNOSIS_SAFE_PROXY_FACTORY_ADDRESS` : Custom Gnosis Safe multisig contract address.
- `CUSTOM_GNOSIS_SAFE_SAME_ADDRESS_MULTISIG_ADDRESS` : Custom Gnosis Safe Same Address Multisig address.
- `CUSTOM_SERVICE_REGISTRY_TOKEN_UTILITY_ADDRESS` : Custom Service Registry Token Utility address.
- `CUSTOM_MULTISEND_ADDRESS` : Custom Multisend address.
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 · 127 lines · 0 tokens per session scan A 4de7ee24251c
autonomy_fetch is a command published in the GitHub repository valory-xyz/open-autonomy (126 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,153 tokens. 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 commands, from other repositories
agentlas-cloud
Staff a task only from the signed-in owner's Agent Cloud agents.
agentlas-local
Staff a task only from Agentlas agents registered on this machine.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
os-meeting
快速创建和管理AI团队会议.
spec-intake
Execute the canonical workflow: .agent/workflows/spec-intake.md.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.