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 skills add fakoli/fakoli-plugins --skill recipe-email-drive-linkgit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/recipe-email-drive-link)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/recipe-email-drive-link"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-email-drive-link/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/skills/fakoli/fakoli-plugins/recipe-email-drive-link"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/recipe-email-drive-link.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.00020 | $0.00355 |
| Opus 5 | $0.00010 | $0.00178 |
| Sonnet 5 | $0.00004 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
recipe-email-drive-link 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 8d 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
Email a Google Drive File Link
Share a Google Drive file and email the link with a message to recipients.
When to Use
Use this workflow when the user wants to share a file from Drive by granting access and sending the link via email in one step.
Workflow
1. Find the file
gws drive files list \
--params '{"q": "name contains 'FILE_NAME'"}' \
--fields "files(id,name,webViewLink)" --format table
2. Grant access
Ask the user what role to grant (reader, writer, commenter):
gws drive permissions create \
--params '{"fileId": "FILE_ID"}' \
--json '{"role": "reader", "type": "user", "emailAddress": "[email protected]"}' \
--dry-run
Confirm, then execute.
3. Send the email with the link
gws gmail +send \
--to [email protected] \
--subject 'SUBJECT' \
--body 'MESSAGE_WITH_LINK' \
--dry-run
Confirm, then send.
Safety
- Always
--dry-runfor both the permission grant and email send - Confirm the access level — don't grant
writerwhenreaderis sufficient
Tips
- The
webViewLinkfrom the file listing is the shareable URL - Use
"type": "anyone"with"role": "reader"for "anyone with the link" sharing
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.
- 8d ago First seen · 58 lines · 20 tokens per session scan A b51a1732b898
recipe-email-drive-link is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 6d ago), licensed MIT. It adds 20 tokens to every session and 355 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-09-03.
Other skills, from other repositories
audit
Read-only quality gate that audits already-built work against its stated requirement and Definition of Done before it is allowed to move to 2done/. Produces a severity-ranked decision proposal (BLOCKER/MAJOR/MINOR/NIT) with evidence, never a fix. Use when an item is claimed complete, before moving anything to 2done/…
pr-vetting
Use when the user wants to thoroughly investigate, vet, review, or security-scan a pull request before deciding how to handle it - especially PRs from external or unknown contributors. Runs a parallel multi-agent investigation (technical, security, value/fit, contributor reputation) and merges the findings into one…
issue-triage
Use when the user wants to triage GitHub issues - decide whether an issue is still relevant, reproducible, closeable, a duplicate, or what concretely needs doing. Selects and prioritizes first (never dumps all issues at once), then deep-triages the chosen issues via parallel subagents, recommends actions for the owner…
requirements-verbatim
Capture a user requirement, decision, approval, or constraint word-for-word into an append-only dated log so it survives context compaction and can never be trimmed, softened, or reinterpreted. Use whenever the user states or approves a requirement, gives a GO, sets a constraint, or makes any decision that later work…
diag
Read-only root-cause diagnosis for a symptom, bug, failure, or unexpected behavior. Establishes the mechanism at file:line and reads up the facts instead of guessing, before any fix is attempted. Produces a diagnosis report; the fix is always a separate step gated by an explicit GO. Use when something is broken…
orchestration
Delegate work to subagents safely and efficiently - decide how many subagents to run, keep parallel tracks on disjoint files, monitor them without flooding your context, inherit security to every subagent, and use return-and-resume so a subagent can ask a question and continue with full context. Use whenever you are…