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 skills/dimaneuron/aiworkers-mcp/aiworkers_mcpnpx skills add dimaneuron/aiworkers-mcp --skill aiworkers_mcpgit clone --depth 1 https://github.com/dimaneuron/aiworkers-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/skills/dimaneuron/aiworkers-mcp/aiworkers_mcp)<a href="https://agentmods.dev/skills/dimaneuron/aiworkers-mcp/aiworkers_mcp"><img src="https://agentmods.dev/badge/skills/dimaneuron/aiworkers-mcp/aiworkers_mcp.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.00227 | $0.04476 |
| Opus 5 | $0.00113 | $0.02238 |
| Sonnet 5 | $0.00045 | $0.00895 |
| Haiku 4.5 | $0.00023 | $0.00448 |
Grade B, and why
aiworkers scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
3. Human runs `aiworkers-mcp login` on the Mac and pastes the token. That writes `~/.config/aiworkers/credentials.json` (`chmod 600`). How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AIWorkers MCP
Thin MCP client. Business logic stays on https://ai.knopka.click. Do not invent tokens or seeds.
Install docs (source of truth): https://github.com/dimaneuron/aiworkers-mcp
Landing: https://ai.knopka.click/mcp
Product: https://ai.knopka.click
If this project has no MCP yet: read that README, install aiworkers-mcp, have the human run aiworkers-mcp login, then aiworkers_whoami and aiworkers_skill_update.
Login (no token in the link)
- Call
aiworkers_login_link(works without a key) and give the human this URL:https://t.me/aiworkersbot?start=mcp - They open it in Telegram, Mini App shows a module token once. Seed of 12 words never goes to chat or to the server.
- Human runs
aiworkers-mcp loginon the Mac and pastes the token. That writes~/.config/aiworkers/credentials.json(chmod 600). - Restart the agent. Call
aiworkers_whoami.
Do not put tokens in git, in mcp.json committed to the repo, or in chat. Prefer aiworkers-mcp login over env in config.
Update MCP (do not mix the three layers)
A tool «not in this session» is not proof it is missing on the server. Cursor caches the tool catalog until the MCP process dies. aiworkers_skill_update only rewrites SKILL.md. It does not restart MCP and does not install new tools. Never use telegram_restart for this.
When the human says «обнови MCP» / «перезапусти MCP», a tool from this skill is missing from the catalog, or the catalog contradicts a live 200/403 from ai.knopka.click:
-
Skill file (what you read). Call
aiworkers_skill_update. Same CLI:aiworkers-mcp skill-update. Writes~/.cursor/skills/aiworkers/SKILL.md(and project.cursor/skills/aiworkers/if you are in a repo with.cursor). Then re-read that file. An old copy in context is stale. -
Running process (tool catalog). Restart the
aiworkersMCP server.- Tell the human: Cursor Settings → MCP → Restart on
aiworkers. - If you can edit config: set env
AIWORKERS_MCP_RELOADin.cursor/mcp.jsonor~/.cursor/mcp.jsonto a new stamp (example20260821-ai-keys), then kill the process:pkill -f aiworkers-mcp. Cursor respawns it. Do not dump the file or anyawp_/awm_/sk-values. - After restart, the catalog must list the tools from this skill (including
ai_keys_issue/ai_chat/tg_channel_createif this skill mentions them). If the catalog still lies, the process did not actually restart.
- Tell the human: Cursor Settings → MCP → Restart on
What ships with it
19 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- __init__.py 202 B runs code
- __main__.py 46 B runs code
- http.py 8.9 KB runs code
- knopka_ai.py 4.6 KB runs code
- knopka_tg.py 5.7 KB runs code
- login.py 4.2 KB runs code
- module_names.py 1.8 KB runs code
- modules/__init__.py 175 B runs code
- modules/_deferred.py 83 B runs code
- modules/ai.py 7.3 KB runs code
- modules/crm.py 2.4 KB runs code
- modules/finance.py 77 B runs code
- modules/surveys.py 9.8 KB runs code
- modules/tasks.py 5.5 KB runs code
- modules/telegram.py 2.8 KB runs code
- modules/tg.py 8.0 KB runs code
- modules/workers.py 13 KB runs code
- server.py 7.4 KB runs code
- skill.py 3.2 KB runs code
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 · 136 lines · 227 tokens per session scan B 4e2c7e50ac56
aiworkers is a skill published in the GitHub repository dimaneuron/aiworkers-mcp (0 stars, last pushed 11d ago), licensed MIT. It adds 227 tokens to every session and 4,476 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…