Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vincentkoc/dotskillsnpx agentmods add skills/vincentkoc/dotskills/graincrawlWrote 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/vincentkoc/dotskills/graincrawl)<a href="https://agentmods.dev/skills/vincentkoc/dotskills/graincrawl"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/graincrawl/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/vincentkoc/dotskills/graincrawl"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/graincrawl.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.00851 |
| Opus 5.5 | $0.00019 | $0.00340 |
| Sonnet 5.5 | $0.00009 | $0.00170 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
graincrawl 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 1mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Graincrawl
Purpose
Maintain graincrawl, the Go CLI that archives Granola notes, transcripts,
panels, people, workspaces, and sync metadata into a private local SQLite store.
Keep it read-only against Granola, SQLite-first for browsing/export, and aligned
with the other crawl apps.
When to use
- Editing or reviewing a
graincrawlcheckout. - Investigating Granola source adapters:
private-api,desktop-cache,encrypted-json,opfs,public-api, orcompanion-cli. - Verifying note, transcript, panel, source object, search, Markdown export, or TUI behavior.
- Preparing a
graincrawlrelease, Homebrew formula, or local binary refresh. - Checking crawlkit control metadata, snapshots, or TUI integration from the app side.
Workflow
-
Locate the
graincrawlcheckout from the current repository, an explicit user path, or the configured workspace root. Read repo-localAGENTS.md,README.md,SPEC.md, anddocs/security.mdbefore release, source-adapter, or unlock work. -
Keep Granola boundaries explicit. Ordinary
doctor,status,notes,export, andtuicommands must not prompt Keychain, unwrap safeStorage, or mutate Granola profile files. -
Use temp
HOME, temp XDG dirs, temp config, and temp SQLite databases for tests and smoke checks. Do not mutate live~/.config/graincrawlarchives or Granola app data unless the user explicitly asks. -
Prefer archived SQLite reads for UI/export behavior. If Markdown export has the data, TUI detail should read that same archived source, not re-query Granola.
-
Run the normal local gate with workspace masking disabled:
GOWORK=off go mod tidy git diff --exit-code -- go.mod go.sum GOWORK=off go vet ./... GOWORK=off go test -count=1 ./... make smoke goreleaser check -
For release work, use semver tags and verify the tap path:
git tag -a v0.1.0 -m "graincrawl v0.1.0" git push origin main v0.1.0 HOMEBREW_NO_AUTO_UPDATE=1 brew install --build-from-source vincentkoc/tap/graincrawl HOMEBREW_NO_AUTO_UPDATE=1 brew test vincentkoc/tap/graincrawl
What ships with it
2 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.
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.
- 1mo ago Changed · +1 lines 0bded3c03e99
- 1mo ago First seen · 87 lines · 47 tokens per session scan A 8eafaf97a1b8
graincrawl is a skill published in the GitHub repository vincentkoc/dotskills (110 stars, last pushed 6d ago), licensed MIT. It adds 47 tokens to every session and 851 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
github-auth
Set up GitHub authentication for the agent using git (universally available) or the gh CLI. Covers HTTPS tokens, SSH keys, credential helpers, and gh auth — with a detection flow to pick the right method automatically.
otto-drive-pr
PR mergeability, CI, and live preview.
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…