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/gpdir16/tabyagent/privacynpx skills add gpdir16/tabyAgent --skill privacygit clone --depth 1 https://github.com/gpdir16/tabyAgentWrote 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/gpdir16/tabyagent/privacy)<a href="https://agentmods.dev/skills/gpdir16/tabyagent/privacy"><img src="https://agentmods.dev/badge/skills/gpdir16/tabyagent/privacy.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 | $0.00020 | $0.04117 |
| Opus 5 | $0.00010 | $0.02058 |
| Sonnet 5 | $0.00004 | $0.00823 |
| Haiku 4.5 | $0.00002 | $0.00412 |
Grade A, and why
privacy 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 3d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 3d ago First seen · 429 lines · 20 tokens per session scan A 4f02e203b601
privacy is a skill published in the GitHub repository gpdir16/tabyAgent (18 stars, last pushed 11d ago), licensed AGPL-3.0. It adds 20 tokens to every session and 4,117 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-08-30.
Other skills, from other repositories
goal-loop
Bootstrap a goal-driven self-improving AutoNudge loop. Give it a goal + anchor directory; it generates LOOP.md + GOAL.md + kanban board, then you write the Definition of Done and arm the loop. The running agent manages the board autonomously: finds issues, adds cards, resolves them, handoffs to Review, repeats until…
spec-workflow
Drive the Kiro CLI v3 spec workflow (Requirements → Design → Tasks → Execution) for the Spec Builder app. Load when authoring a spec inside a spec-builder worker slot, or when the seed prompt references a spec directory and a spec type.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
browser-workflow-skill-builder
Create robust browser automation skills for sites like LinkedIn, X/Twitter, YouTube, Stripe, or other logged-in web apps by saving page context, analyzing HTML/CSS, writing skill-local JS extract/verify scripts, and using CSS selector actions with screenshot verification.
pr-integration-test
Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.
publish
Publish the Octop Python package: cut a release branch from develop, bump version, update CHANGELOG, open a PR to main; after merge, Actions tag on main (PyPI / Docker Hub) and sync main into develop. Use when the user asks to publish, release, bump version, cut a release, or run /publish.