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 Stijnman/grok-custom-skills --skill drive-persistence-bridgegit clone --depth 1 https://github.com/Stijnman/grok-custom-skillsWrote 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/stijnman/grok-custom-skills/drive-persistence-bridge)<a href="https://agentmods.dev/skills/stijnman/grok-custom-skills/drive-persistence-bridge"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/drive-persistence-bridge/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/stijnman/grok-custom-skills/drive-persistence-bridge"><img src="https://agentmods.dev/badge/skills/stijnman/grok-custom-skills/drive-persistence-bridge.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.00049 | $0.00597 |
| Opus 5 | $0.00024 | $0.00298 |
| Sonnet 5 | $0.00010 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
drive-persistence-bridge 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drive Persistence Bridge
Use this skill to preserve named artifacts safely across local storage and an approved remote destination. It supports backup preparation, version comparison, restore planning, and approved uploads; it does not authorize autonomous synchronization or publication.
Workflow
- Confirm the source files, destination service and folder or repository, retention expectation, and whether the request is local-only, upload, restore, or comparison.
- Inspect available connector capabilities and permissions. Use read-only discovery first; do not assume a destination, branch, folder, account, or tool schema.
- Build a local, timestamped artifact with a clear name. Record its checksum, source scope, creation time, and a concise description. Exclude secrets, credentials, cache directories, and unnecessary personal data.
- For a remote upload, repository commit or push, restoration that overwrites files, retention cleanup, or deletion, present a preview of the exact targets and changes. Obtain explicit user approval before proceeding.
- Execute only the approved operation with least privilege. Verify the returned identifier, link, commit reference, or checksum.
- Report what completed, where it was stored, how to restore it, and any failed steps. Keep local artifacts intact when a remote operation fails.
Restore and Version Comparison
List available versions with dates, checksums, sizes, and source descriptions. Compare candidate versions before restoration and use a dry run where available. Require approval before overwriting local or remote data, and preserve a rollback copy before any approved overwrite.
Reliability
Retry only idempotent, transiently failed operations a small bounded number of times. Stop for authentication, permission, conflict, or capability failures; explain the blocker and offer a local export or manual-upload alternative. Never claim a remote backup, sync, commit, or restore succeeded without verified evidence.
What ships with it
1 file 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.
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 · 41 lines · 49 tokens per session scan A 142ec40dcc01
drive-persistence-bridge is a skill published in the GitHub repository Stijnman/grok-custom-skills (9 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 597 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
goal-meta-skill
A guide for turning an unclear or complex task into a reviewable /goal instruction for coding agents.
workflow-to-skill
Turn a goal and existing CLI, MCP, HTTP, API, or external workflow capabilities into one reviewable reusable Agent Skill. Use when the user asks to create or revise a workflow SKILL.md without a dedicated interface for invocation or result presentation. A webpage, UI, image, or report produced as workflow output does…
rss-digest
Collect RSS or Atom sources and produce a traceable intelligence digest through the configured Weft workflow.
workflow-docs-sync
A project-documentation synchronisation workflow for rebuilding project facts from a local Git folder, GitHub repository, or current working directory, then updating core workflow documents.
workflow-to-skill-with-surface
Create or revise one reusable workflow Skill plus an optional harness-native Prompt Surface that maps a dedicated form, Page, button set, command UI, or result view to ordinary Skill messages and Harness results. Use only when the user explicitly requests a dedicated interface for invoking the Skill or presenting its…
setup-matt-pocock-skills
A setup skill that configures engineering skills for a repository, including its issue tracker, labels, and documentation layout. A repository is the project folder managed by version control.