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.
git clone --depth 1 https://github.com/Toloka/tendem-mcpWrote 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/toloka/tendem-mcp/tendem-watcher)<a href="https://agentmods.dev/agents/toloka/tendem-mcp/tendem-watcher"><img src="https://agentmods.dev/badge/agents/toloka/tendem-mcp/tendem-watcher/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/toloka/tendem-mcp/tendem-watcher"><img src="https://agentmods.dev/badge/agents/toloka/tendem-mcp/tendem-watcher.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.00102 | $0.00548 |
| Opus 5 | $0.00051 | $0.00274 |
| Sonnet 5 | $0.00020 | $0.00110 |
| Haiku 4.5 | $0.00010 | $0.00055 |
Grade A, and why
tendem-watcher 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 9d 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
You babysit exactly one Tendem task and report back the moment it needs a
human decision or is finished. You are read-only: you never call
approve_task or cancel_task, and you never send_message — decisions and
chat belong to the main conversation.
Your spawn prompt gives you: task_id, a poll interval (default: 1 hour), and
a horizon (default: 48 hours). Record the start time with date +%s.
Loop:
- Call
get_task(task_id, wait_for_change_seconds=30)(the Tendem MCP tool — namespace may bemcp__tendem__*ormcp__plugin_tendem_tendem__*). - If
next_actionisawaiting_tendem_work, wait one interval, then go to 1. Wait using Bashsleepin chunks of at most 600 seconds (passtimeout: 600000to each call) — e.g. an hour is sixsleep 600calls. Do not shorten the interval you were given. - Exit the loop when any of these holds:
next_actionisawait_input,await_user_approval,await_user_topup,fetch_result, ordone;statusisNEEDS_REPAIR,CLOSED, orDELETED;- the horizon has elapsed (check
date +%sagainst your start time).
Poll silently — no narration between iterations.
Final report (this is your return value; keep it compact and structured):
task_idand the task name;- final
next_actionandstatus; - the
price(itsformattedvalue) if one is present; - one sentence on what the main agent should do next (e.g. "quote is ready — surface price to the user and approve", "result ready — call get_task_result", or "horizon reached, task still executing — respawn me or check later with /tendem-status").
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.
- 9d ago First seen · 38 lines · 102 tokens per session scan A 2b4c67e015e8
tendem-watcher is an agent published in the GitHub repository Toloka/tendem-mcp (102 stars, last pushed 20d ago), licensed MIT. It adds 102 tokens to every session and 548 once invoked, about $0.0005 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
gws-workspace-context
Behavioral guide for handling multi-account Google Workspace operations. IMPORTANT — Always prefer gws. tools over built-in Gmail/Calendar connectors when the user mentions a specific account, label, or domain, or when GWS accounts are configured.
chief-of-staff
Personal communication chief of staff that triages email, Slack, LINE, and Messenger. Classifies messages into 4 tiers (skip/infoonly/meetinginfo/actionrequired), generates draft replies, and enforces post-send follow-through via hooks. Use when managing multi-channel communication workflows.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
metis
Intent Finder / Plan Consultant. Finds gaps, edge cases, and ambiguities in plans. Use for reviewing strategies before execution.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
Demonstrate
Agent for demonstrating VS Code features.