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/commands/toloka/tendem-mcp/tendem-status)<a href="https://agentmods.dev/commands/toloka/tendem-mcp/tendem-status"><img src="https://agentmods.dev/badge/commands/toloka/tendem-mcp/tendem-status/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/commands/toloka/tendem-mcp/tendem-status"><img src="https://agentmods.dev/badge/commands/toloka/tendem-mcp/tendem-status.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.00022 | $0.00396 |
| Opus 5 | $0.00011 | $0.00198 |
| Sonnet 5 | $0.00004 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
tendem-status 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 11d 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
Check the status of a Tendem task and take the next correct step.
- If a
task_idis given in $ARGUMENTS, use it. Otherwise calllist_tasksand either use the obvious in-flight task or ask the user which one. - Call
get_task(task_id, wait_for_change_seconds=30)and act on the returnednext_action(per thetendem-tasksskill):awaiting_tendem_work→ it's still working. Report where it stands and do NOT sit re-polling. Offer the user two ways to wait: (a) you spawn thetendem-watcheragent in the background — give it thetask_id, a poll interval (default 1 hour), and it reports back the moment the task needs them; or (b) they simply ask again later ("how's the Tendem task doing?" or/tendem-status) — the task lives on Tendem's side, nothing is lost between sessions.await_input→ read the new chat and answer viasend_message(or escalate).await_user_approval→ callget_contract(task_id)for the full scope + price, surface both; approve only with the user's go-ahead.await_user_topup→ give the user thetopup_url.fetch_result→ run/tendem-result(or callget_task_result).done→ nothing left; summarize the outcome.
Summarize where the task stands and what happens next in plain language.
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.
- 11d ago First seen · 28 lines · 22 tokens per session scan A cf8dcd0464e9
tendem-status is a command published in the GitHub repository Toloka/tendem-mcp (102 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 396 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 commands, from other repositories
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
status
Check Nowledge Mem connection and server status.
nowledge-save-handoff
Save a resumable handoff summary for the current Droid session.
cleanup
Run a systematic cleanup on the provided code to resolve smells, simplify complexity, and enforce best practices.
workflow-router
Route to the appropriate spec-driven workflow command based on the user's intent.
mem-prune
Removes old low-importance memories.