Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/lbb00/ai-rules-sync/new-adapter)<a href="https://agentmods.dev/skills/lbb00/ai-rules-sync/new-adapter"><img src="https://agentmods.dev/badge/skills/lbb00/ai-rules-sync/new-adapter.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.1 | $0.00021 | $0.00626 |
| Opus 5 | $0.00010 | $0.00313 |
| Sonnet 5 | $0.00004 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
new-adapter 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 6d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Adapter
Instructions
Complete workflow for adding support for a new AI tool to AIS.
Prerequisites
Before starting, gather this information:
- Tool name (e.g., "windsurf", "mcp")
- Rule/config types supported (e.g., rules, commands, skills)
- Default source directory (e.g.,
.windsurf/rules/) - Target directory (usually same as source)
- File mode:
fileordirectory
Steps
1. Create Adapter File
Create src/adapters/<tool>-<type>.ts:
import { createBaseAdapter } from './base.js';
export const myToolAdapter = createBaseAdapter({
name: '<tool>-<type>',
tool: '<tool>',
subtype: '<type>',
configPath: ['<tool>', '<type>'],
defaultSourceDir: '.<tool>/<type>',
targetDir: '.<tool>/<type>',
mode: 'directory', // or 'file'
});
2. Register Adapter
In src/adapters/index.ts:
- Import the new adapter
- Register in
DefaultAdapterRegistryconstructor
3. Update Project Config
In src/project-config.ts:
- Add tool section to
ProjectConfiginterface - Add tool to
SourceDirConfiginterface if needed
4. Wire CLI Commands
In src/cli/register.ts:
- Add tool subcommand group
- Register add/remove/install/import commands
5. Update Completion
In src/completion.ts:
- Add tool to completion types
- Add subtype completions
In src/completion/scripts.ts:
- Update bash/zsh/fish completion scripts
6. Add Tests
Create src/__tests__/<tool>-<type>.test.ts:
- Test adapter properties
- Test add/remove operations
- Test config path resolution
7. Update Documentation
- README.md: Add to supported sync types table
- README_ZH.md: Sync changes (use
/sync-readme) - CLAUDE.md: Update if architectural changes
8. Verify
# Build
npm run build
# Run tests
npm test
# Test manually
node dist/index.js <tool> <type> add <name>
node dist/index.js <tool> <type> remove <name>
Checklist
- Adapter file created
- Adapter registered
- ProjectConfig updated
- CLI commands wired
- Completion updated
- Tests written and passing
- README.md updated
- README_ZH.md synced
- Manual testing complete
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.
- 6d ago First seen · 111 lines · 21 tokens per session scan A 66e3a8a4bc72
new-adapter is a skill published in the GitHub repository lbb00/ai-rules-sync (37 stars, last pushed 16d ago), licensed Unlicense. It adds 21 tokens to every session and 626 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
authoring-skills-and-rules
Author Skills (SKILL.md) and rules/instructions across Claude Code, Cursor, OpenCode, Codex, and GitHub Copilot. Covers frontmatter, file layout, activation model, cross-platform mirroring, and the universal craft: progressive disclosure, trigger-rich descriptions (context pointers), leading words, token budget…
karpathy-guidelines
Tool-agnostic behavioral guidelines for AI coding assistants. Use when writing, reviewing, debugging, or refactoring code to reduce overengineering, surface ambiguity, make surgical changes, and define verifiable success criteria.
spec-driven
Structured planning pipeline with 4 adaptive phases (Specify, Design, Tasks, Execute) and persistent knowledge accumulation for development teams. Auto-sizes depth by complexity from quick fixes to multi-component features. Commands: /explore (understand problem + map context), /plan (write spec → design → tasks)…
skill-memory
Use skill-memory to download, view and edit agent skills in memory. TRIGGER by 'skill', 'memory', 'learn'.
valyu-best-practices
Complete Valyu API toolkit for AI agents. Use this skill when asked to perform real-time search across web, academic, medical, transportation, financial sources, content extraction from URLs, AI-powered answers with citations, or comprehensive deep research reports.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…