agentmods.dev

synlin CLAUDE.md

Repository instructions for synlin, a command-line tool that manages reusable Claude Code configuration such as skills, agents, commands, rules, and templates. They describe its code layout, library location, and safe file-writing rules.

In plain words
What is it for?
Use them when changing synlin's catalog, installer, manifest, file-resolution, or command-handling code, and when checking how changes should be verified.
Why use it?
They explain which files belong to the tool and which belong to the user's separate configuration library. This helps prevent accidental changes to user data while developing or testing the command-line tool.

Instructions file

2 2mo ago A scan 628 tokens original MIT
View the source file tylld/synlin
Install

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.

agentmods
npx agentmods add instructions/tylld/synlin/claude-md
Clone the repo
git clone --depth 1 https://github.com/tylld/synlin
Per session 628 This file is loaded in full into every session.
When invoked 628 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00628 $0.00628
Opus 5 $0.00314 $0.00314
Sonnet 5 $0.00126 $0.00126
Haiku 4.5 $0.00063 $0.00063

Measured 2d ago against content hash 02f28a5157e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

synlin CLAUDE.md 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 2d 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.

CLAUDE.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

synlin — Claude Code Instructions

CLI that manages a personal library of Claude Code config items (skills, agents, commands, rules, templates) and installs them into projects' .claude/ dirs.

Layout

  • src/lib/ — pure core: catalog scan, manifest, tree hashing, installer, name resolution, tool adapters. All side-effect-light and unit-tested.
  • src/commands/ — thin command handlers over src/lib/; interactive prompts (@clack/prompts) stay at this layer only.
  • The library is NOT in this repo. It is the user's own directory, resolved via SYNLIN_LIBRARY → libraryRoot in ~/.config/synlin/config.json → ~/.synlin/library (see resolveLibraryRoot). synlin library init bootstraps a new one. Andrei's personal library lives in the separate private repo ~/Documents/ai-playground/synlin-library.
  • scripts/seed.ts — one-time initial import into the resolved library; do not re-run casually (it refuses unless the library is empty or --force is passed).

Rules

  • Never modify library content as a side effect of CLI code changes — the library is user data, wherever it lives.
  • Every file write/delete in a target project must stay inside the project's write envelope: the tool config dirs (.claude/, .codex/, .cursor/, .opencode/), adapter-declared shared files at the project root (currently AGENTS.md), and <projectRoot>/.synlin.json. Owned-tree writes for tool T must additionally stay inside T's own config dir (see assertWritable / assertInside in src/lib/paths.ts); keep that guarantee when touching the installer or adapters.
  • The manifest format (<projectRoot>/.synlin.json, version 2) is a compatibility contract — bump MANIFEST_VERSION and add migration on breaking changes. Version 1 (.claude/.synlin.json) is migrated in memory on read and persisted (legacy file deleted) on the next write.
  • Tool adapters (src/lib/tools/) must render deterministically: pure functions of library item content — no clocks, env, or fs beyond the item.
  • Tests run against tmp-dir fixtures (tests/helpers/tmp.ts); command handlers accept an injectable Runtime (cwd, env, interactive) — never depend on process.cwd() inside src/lib/.

Read the full file on GitHub · 49 lines

Changes

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.

  1. 2d ago First seen · 49 lines · 628 tokens per session scan A 02f28a5157e7

Subscribe to this mod's changes

synlin CLAUDE.md is an instructions file published in the GitHub repository tylld/synlin (2 stars, last pushed 2mo ago), licensed MIT. It adds 628 tokens to every session, about $0.0031 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-31.

Writing and docs
Related

Other instructions, from other repositories

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens