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/ntrpydev/proton-workflow-connector/setupnpx skills add NtrpyDev/proton-workflow-connector --skill setupgit clone --depth 1 https://github.com/NtrpyDev/proton-workflow-connectorWrote 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/ntrpydev/proton-workflow-connector/setup)<a href="https://agentmods.dev/skills/ntrpydev/proton-workflow-connector/setup"><img src="https://agentmods.dev/badge/skills/ntrpydev/proton-workflow-connector/setup.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.1 | $0.00031 | $0.00363 |
| Opus 5 | $0.00015 | $0.00181 |
| Sonnet 5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
proton-workflow-connector-setup 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 6d 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
Proton Workflow Connector setup
Use this skill to configure or troubleshoot the Proton Workflow Connector.
Rules:
- Keep all setup generic. Do not add personal mailbox examples, private IPs, local usernames, Bridge passwords, SimpleLogin API keys, message bodies, screenshots, or logs to the repo.
- Remind the user this connector is unofficial and not affiliated with Proton AG.
- Prefer local stdio unless the user explicitly needs Streamable HTTP.
- For locally hosted agents that support MCP, use stdio first and localhost HTTP when the client needs a URL.
- For remote HTTP, follow
docs/HOSTING.mdand require HTTPS, OAuth, Host/Origin validation, and network controls. - Use
list_foldersfirst to verify account folder names before moving, trashing, or archiving messages. - Treat
permanently_delete_messageas destructive and require explicit user intent. - Pass
confirm=trueonly after the user explicitly approves an irreversible operation. - Bulk operations must use explicit numeric IMAP UIDs and respect
PROTON_MCP_BULK_LIMIT.
Setup steps:
- Install Proton Mail Bridge and confirm it is running.
- Copy
.env.exampleto a private path outside git. - Fill Bridge host, ports, username, generated Bridge password, and sender email from the Bridge app.
- Optionally add
SIMPLELOGIN_API_KEY. - Install the Python package with
python -m pip install -e .. - Add the MCP server to the user's client.
- Verify with
list_folders, then a narrowsearch_mail.
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.
- 6d ago First seen · 31 lines · 31 tokens per session scan A 72d685b1c4e3
proton-workflow-connector-setup is a skill published in the GitHub repository NtrpyDev/proton-workflow-connector (0 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 363 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…