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/0-soft/manus-mcp/agent.listgit clone --depth 1 https://github.com/0-SOFT/Manus-MCPWhat 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.00237 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
agent.list 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 2d 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.
What it actually says
agent.list - Manus API
Talk to an agent: Use task.sendMessage with the agent’s task_id to send messages to an agent’s main task. See the Agents guide.
Authorizations
x-manus-api-key
string
header
required
Response
200
application/json
Agents retrieved successfully.
ok
boolean
Whether the request was successful.
Example:
true
request_id
string
Unique identifier for this API request.
data
object[]
Array of agent objects.
Hide child attributes
data.id
string
Unique identifier for the agent. Use this as agent_id in task.list (with scope=agent_subtask) to view this agent's subtasks.
data.task_id
string
The task ID associated with this agent's creation or configuration. Use task.detail to view the associated task.
data.nickname
string
Display name of the agent. Can be updated via agent.update.
data.about
string
Description or bio of the agent explaining its purpose and specialization. Can be updated via agent.update.
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.
- 2d ago First seen · 71 lines · 0 tokens per session scan A 9b0af3e720fe
agent.list is an agent published in the GitHub repository 0-SOFT/Manus-MCP (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 237 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-31.
Other agents, from other repositories
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
chainaware-rug-pull-detector
Specialized Web3 rug pull detection agent powered by ChainAware's Behavioral Prediction MCP. Use this agent PROACTIVELY whenever a user wants to check if a smart contract, liquidity pool, DeFi token, or new project is safe to invest in or deposit funds into. Automatically invoke when the user provides a contract…
onboarding
Onboard new projects with zen analysis configuration.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
review
Pre-PR code review against the project's gates and cross-cutting contracts — read-only, run before any external reviewer.
web-performance-auditor
Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.