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 yu-iskw/coding-agent-fabric --skill sync-readmegit clone --depth 1 https://github.com/yu-iskw/coding-agent-fabricWrote 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/yu-iskw/coding-agent-fabric/sync-readme)<a href="https://agentmods.dev/skills/yu-iskw/coding-agent-fabric/sync-readme"><img src="https://agentmods.dev/badge/skills/yu-iskw/coding-agent-fabric/sync-readme/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/yu-iskw/coding-agent-fabric/sync-readme"><img src="https://agentmods.dev/badge/skills/yu-iskw/coding-agent-fabric/sync-readme.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.00021 | $0.00552 |
| Opus 5.5 | $0.00008 | $0.00221 |
| Sonnet 5.5 | $0.00004 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
sync-readme 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 1mo 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sync-readme
Use this skill to keep the technical documentation (README.md and CONTRIBUTING.md) up-to-date with the codebase.
When to Use
- After adding or renaming packages in the monorepo.
- After adding or modifying root scripts in
package.json. - After adding or changing CLI commands or subcommands.
- After significant architectural changes or package relationship updates.
Workflow
-
Analyze Project State: Directly observe the project to gather the necessary information:
- Layout: List directories in
packages/andpackages/plugins/to see the monorepo structure. - Scripts: Read the root
package.jsonto see available scripts. - Commands: Read CLI command definitions in
packages/cli/src/commands/to identify commands and subcommands.
- Layout: List directories in
-
Locate Sync Markers: Find the following markers in the documentation files:
<!-- SYNC:LAYOUT -->...<!-- /SYNC:LAYOUT --><!-- SYNC:SCRIPTS -->...<!-- /SYNC:SCRIPTS --><!-- SYNC:COMMANDS -->...<!-- /SYNC:COMMANDS --><!-- SYNC:ARCHITECTURE -->...<!-- /SYNC:ARCHITECTURE -->
-
Update Content: Update the content between the markers based on your observations:
- Layout ->
SYNC:LAYOUT(usually inCONTRIBUTING.md): List packages and their descriptions from their respectivepackage.jsonfiles. - Scripts ->
SYNC:SCRIPTS(usually inCONTRIBUTING.md): Format scripts from the rootpackage.jsonas a bulleted list. - Commands ->
SYNC:COMMANDS(usually inREADME.md): Format CLI commands as markdown headings with bash examples. - Architecture ->
SYNC:ARCHITECTURE(usually inCONTRIBUTING.md): Review and update the Mermaid diagram if package relationships or key components have changed.
- Layout ->
-
Preserve Formatting: Ensure that you keep the markers themselves and only update the content between them. Use appropriate markdown blocks (code blocks, lists) that match the existing documentation style.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 46 lines · 21 tokens per session scan A 960095d7c250
sync-readme is a skill published in the GitHub repository yu-iskw/coding-agent-fabric (1 stars, last pushed 19d ago), licensed Apache-2.0. It adds 21 tokens to every session and 552 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
delegate-coding-agent
Route coding work to another local coding-agent CLI through the llm-provider MCP server. Use when a task benefits from a powerful model for difficult reasoning or a faster, lower-cost model for bounded implementation, tests, investigation, or review.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-cloud-functions
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.
verify
Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
customer-deck-builder
Build tailored customer-facing sales or customer success decks from approved account context and generate the presentation with Gamma through Zapier MCP.
deep-research
Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 8 modes: full research, quick brief, paper review, lit-review, fact-check, three-way literature scan, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question…