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 Howie126313/obsidian-vault-kit --skill github-syncgit clone --depth 1 https://github.com/Howie126313/obsidian-vault-kitWrote 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/howie126313/obsidian-vault-kit/github-sync)<a href="https://agentmods.dev/skills/howie126313/obsidian-vault-kit/github-sync"><img src="https://agentmods.dev/badge/skills/howie126313/obsidian-vault-kit/github-sync/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/howie126313/obsidian-vault-kit/github-sync"><img src="https://agentmods.dev/badge/skills/howie126313/obsidian-vault-kit/github-sync.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.00040 | $0.00737 |
| Opus 5.5 | $0.00016 | $0.00295 |
| Sonnet 5.5 | $0.00008 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
github-sync 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Sync — Subagent Dispatcher
When this skill is triggered, do not execute sync steps yourself. Immediately use the Agent tool to launch an independent subagent in the background to handle the entire sync workflow.
Dispatch
Call the Agent tool with the following parameters:
Agent({
description: "GitHub Sync",
model: "sonnet",
run_in_background: true,
mode: "bypassPermissions",
prompt: <full content of the sync-workflow block below>
})
After dispatching, inform the user that sync has started in the background. They can continue other work and will be notified on completion.
sync-workflow
Pass the following content as the Agent prompt (copy verbatim, do not modify):
Step 1: Environment Detection & Status Check
1a. Detect project root and remote (run in parallel):
git rev-parse --show-toplevel # project root
git remote get-url origin # remote URL
git branch --show-current # current branch
1b. Check Git status:
git status
git diff --stat
If there are no changes (no unstaged modifications, no untracked files), output "Nothing to sync" and end.
Step 2: Analyze Changes and Update README.md
2a. Categorize all changed files into three groups:
- Added: new articles or directories
- Modified: updated content
- Deleted: removed content
2b. Update README.md:
- Read current README.md content
- Use
Glob("**/*.md")to scan the project directory structure, count Markdown files (exclude .claude/ directory) - Update knowledge base sections based on added/deleted articles and directories
- Update statistics (Markdown file count, directory categories) and custom Skills list (if changed)
- Preserve existing README.md format and style
Update principle: only update sections with actual changes, do not rewrite unnecessarily.
Step 3: Commit and Push
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 First seen · 96 lines · 40 tokens per session scan A 39d7a18ca23b
github-sync is a skill published in the GitHub repository Howie126313/obsidian-vault-kit (3 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 737 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-31.
Other skills, from other repositories
pr-create
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Activate when the user says "create pr", "make a pr", "open pull request", "submit pr", "pr for these changes", or wants to get their current work into a reviewable PR. Assumes the project uses git, is hosted on…
create-release-checklist
Create a release checklist and GitHub issue for an R package. Use when the user asks to "create a release checklist" or "start a release" for an R package.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
watch-pr
Watch an Elixir/Phoenix PR for new review comments (bot + human) and CI results via a background watcher that wakes Claude only on real events. Use after opening a PR or pushing, while waiting on CI or reviewers.
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.