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 Abilityai/abilities --skill syncgit clone --depth 1 https://github.com/Abilityai/abilitiesWrote 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/abilityai/abilities/sync)<a href="https://agentmods.dev/skills/abilityai/abilities/sync"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/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/abilityai/abilities/sync"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/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.00028 | $0.10279 |
| Opus 5.5 | $0.00011 | $0.04112 |
| Sonnet 5.5 | $0.00006 | $0.02056 |
| Haiku 4.5 | $0.00003 | $0.01028 |
Grade B, and why
sync scanned grade B with 2 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -v ".claude/debug/" | \ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
The `mcp__trinity__*` tools below need a live connection. If they're unavailable (or a call errors with no connection), run **`/trinity:connect`** — it authenticates and writes `.mcp.json` (or refreshes it from your stor How it starts
The opening of the file, as written. The whole thing — 913 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Synchronization Skill
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.sync vX.Y — recent: <summary>. Then proceed.
Synchronize the local agent with one or more remote instances on Trinity. Supports multiple remotes (e.g., production, staging, development) and branch-based versioning.
Prerequisite — Trinity MCP connection
The mcp__trinity__* tools below need a live connection. If they're unavailable (or a call errors with no connection), run /trinity:connect — it authenticates and writes .mcp.json (or refreshes it from your stored profile) — then reconnect with /mcp (full restart only as a fallback) and resume. Never fall back to the Trinity CLI or curl.
Multi-Remote Architecture
A single local agent can have multiple remote counterparts on Trinity:
┌─────────────────────┐
│ LOCAL AGENT │
│ (development) │
└─────────┬───────────┘
│
┌─────┴─────┬──────────────┐
▼ ▼ ▼
┌────────┐ ┌─────────┐ ┌──────────────┐
│ prod │ │ staging │ │ dev │
│ @main │ │ @staging│ │ @experimental│
│ ───────│ │ ────────│ │ ─────────────│
│my-agent│ │my-agent │ │my-agent-dev │
│ │ │-staging │ │ │
└────────┘ └─────────┘ └──────────────┘
Trinity Platform Instances
Configuration
Remote instances are configured in .trinity-remote.yaml at the agent root. This is the single registry of this agent's remote Trinity instances — the same file /trinity:onboard writes at deploy time and /trinity:loop reads to find its remote counterpart. Sync owns the multi-remote and branch fields; onboard maintains the deploy-tracking fields (instance, profile, deployed_at).
# .trinity-remote.yaml
# Remote Trinity instances of this agent.
# instance / profile / deployed_at are machine-maintained by onboard — safe to leave as-is.
default: prod # Which remote to use when none specified
remotes:
prod:
agent: my-agent # Trinity agent name (sync)
branch: main # Branch this remote tracks (sync)
instance: https://trinity.example.com # Trinity URL deployed on (onboard)
profile: default # CLI profile to reach it (onboard)
deployed_at: 2026-06-16T12:00:00Z # Last deploy, ISO 8601 (onboard)
description: Production instance
staging:
agent: my-agent-staging
branch: staging
description: Staging for testing
dev:
agent: my-agent-dev
branch: experimental
description: Development/experimental
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.
- 7d ago Changed · +3 lines 93f65e0fc9c1
- 16d ago Changed · +1 lines f51064edbd15
- 1mo ago Changed · +1 lines 0c0804335f4a
- 1mo ago First seen · 908 lines · 28 tokens per session scan B 2beef981e13c
sync is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 10,279 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-07.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…