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.
git clone --depth 1 https://github.com/alinaqi/maggyWrote 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/commands/alinaqi/maggy/sync-contracts)<a href="https://agentmods.dev/commands/alinaqi/maggy/sync-contracts"><img src="https://agentmods.dev/badge/commands/alinaqi/maggy/sync-contracts/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/commands/alinaqi/maggy/sync-contracts"><img src="https://agentmods.dev/badge/commands/alinaqi/maggy/sync-contracts.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.00000 | $0.01913 |
| Opus 5.5 | $0.00000 | $0.00765 |
| Sonnet 5.5 | $0.00000 | $0.00383 |
| Haiku 4.5 | $0.00000 | $0.00191 |
Grade A, and why
sync-contracts 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 2mo 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sync-contracts
Lightweight incremental update of workspace contracts without full re-analysis.
Purpose
Fast contract synchronization that:
- Checks only contract source files (not full workspace)
- Updates CONTRACTS.md with changes
- Validates consistency
- Takes ~15 seconds instead of ~2 minutes
When to Use
| Scenario | Command |
|---|---|
| After modifying API endpoints | /sync-contracts |
| After changing shared types | /sync-contracts |
| Session start shows stale contracts | /sync-contracts |
| Post-commit hook (automatic) | /sync-contracts --lightweight |
| Before pushing changes | /sync-contracts --validate |
| See what changed without updating | /sync-contracts --diff |
Behavior
Step 1: Load Existing Topology
🔄 Loading workspace context...
Workspace: myapp (Monorepo)
Last full analysis: 2026-01-18T10:00:00Z
Last sync: 2026-01-20T14:32:00Z
Does NOT re-discover workspace structure - uses existing TOPOLOGY.md.
Step 2: Check Contract Sources
📋 Checking contract sources...
Monitored files (from .contract-sources):
✓ apps/api/openapi.json (modified 2h ago)
✓ packages/shared-types/src/index.ts (modified 2h ago)
○ packages/db/schema/campaigns.ts (unchanged)
○ packages/db/schema/users.ts (unchanged)
○ apps/api/app/schemas/campaign.py (unchanged)
Changes detected: 2 files
Step 3: Extract Changes
📝 Extracting contract changes...
apps/api/openapi.json:
+ POST /api/campaigns/bulk (new endpoint)
~ GET /api/campaigns (added 'status' query param)
packages/shared-types/src/index.ts:
~ Campaign interface (added 'tags: string[]' field)
+ CampaignBulkCreate interface (new)
Step 4: Update Artifacts
✏️ Updating workspace artifacts...
Updated: _project_specs/workspace/CONTRACTS.md
- Added POST /api/campaigns/bulk to endpoints
- Updated Campaign type definition
- Added CampaignBulkCreate type
Updated: _project_specs/workspace/CROSS_REPO_INDEX.md
- Added bulk create capability
Timestamps updated:
Last sync: 2026-01-20T16:45:00Z
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.
- 2mo ago First seen · 338 lines · 0 tokens per session scan A 0a92da9d2478
sync-contracts is a command published in the GitHub repository alinaqi/maggy (711 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,913 tokens. 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.
sync-contracts compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sync-contractsalinaqi/maggy | Command | 711 | 24d ago | MIT | A | 0 | Claude Code |
| python-reviewloulanyue/awesome-claude-notes | Command | 271 | 1mo ago | MIT | A | 31 | Claude Code |
| frappe-backendDkm0315/frappe-agent | Command | 27 | 27d ago | MIT | A | 0 | Claude Code, Cursor |
| py-hardenmathisk2095/jko-claude-plugins | Command | 3 | 24d ago | MIT | A | 32 | Claude Code |
| py-structuremathisk2095/jko-claude-plugins | Command | 3 | 24d ago | MIT | A | 23 | Claude Code |
| skill-mcp-serverdewtech-technologies/dare-method | Command | 5 | 3mo ago | MIT | A | 0 | Claude Code |
| skill-fastapi-apidewtech-technologies/dare-method | Command | 5 | 3mo ago | MIT | A | 0 | Claude Code |