What is speckit.sync-template?

A repository updater that checks the current version of Cisco's shared repository template and can find a newer release.

Use it to check for a newer template release, sync to the latest release, force an update, or sync to a specified version while respecting skipped files.

It avoids manually comparing your project with the upstream template and helps keep shared files up to date. It can preview changes before writing them.

How caipe-io/ai-platform-engineering configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to caipe-io/ai-platform-engineering. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/caipe-io/ai-platform-engineering/main/.claude/skills/speckit.sync-template/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/caipe-io/ai-platform-engineering

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/speckit.sync-template.svg)](https://agentmods.dev/skills/caipe-io/ai-platform-engineering/speckit.sync-template)

Your own site

<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/speckit.sync-template"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/speckit.sync-template.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,068 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Data Exfiltration · line 33
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
medium Agent Snooping · line 98
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01068
Opus 5	$0.00000	$0.00534
Sonnet 5	$0.00000	$0.00214
Haiku 4.5	$0.00000	$0.00107

Measured 8d ago against content hash 311ae9fafce2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

speckit.sync-template 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 8d 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/skills/speckit.sync-template/SKILL.md · 100 lines

How it starts

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

description: Sync with upstream repo-template updates scripts: sh: scripts/bash/sync-template.sh "$ARGUMENTS"

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty). Valid arguments: --check (preview only, no writes), --force (apply without prompting), a specific version string like v1.2.0.

Outline

You are syncing this repository with the upstream cisco-eti/repo-template. Follow these steps exactly.

Step 1 — Read current state

Read .specify/upstream.yml.
- Extract source (e.g., cisco-eti/repo-template), version (current applied version), overrides (list of files to skip).
If .specify/upstream.yml does not exist, halt and tell the user: "This repo has no .specify/upstream.yml. Initialize it first using the template at cisco-eti/repo-template."

Step 2 — Discover latest release

Use the GitHub API to find the latest release of the upstream repo: GET https://api.github.com/repos/<source>/releases/latest
Extract tag_name (e.g., v1.1.0) and assets (find the ZIP asset and manifest.json asset).
If the user specified a version in $ARGUMENTS, use that version instead of latest.
Compare tag_name to current version:
- If equal: report "Already at latest version . Nothing to do." and stop (unless --force was passed).

Step 3 — Read the manifest

Download manifest.json from the release assets.
Parse:
- semver_bump: "major", "minor", or "patch"
- changed_files: list of files changed in this release
- breaking_files: list of files with breaking changes
- changelog_url: link to view details

Step 4 — Determine what to apply

Start with changed_files from the manifest.
Remove any file listed in .specify/upstream.yml overrides — these are skipped.
Remaining files = apply set.
Intersect apply set with breaking_files → breaking set (files in apply set that are also breaking).

Read the full file on GitHub · 100 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.

8d ago First seen · 100 lines · 0 tokens per session scan A 311ae9fafce2

Subscribe to this mod's changes

speckit.sync-template is a skill published in the GitHub repository caipe-io/ai-platform-engineering (407 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,068 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.

Git and workflow agent-orchestration agentic-ai ai-agents caipe multi-agent-systems platform-engineering

ai-platform-engineering: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

description: Sync with upstream repo-template updates scripts: sh: scripts/bash/sync-template.sh "$ARGUMENTS"

User Input

Outline

Step 1 — Read current state

Step 2 — Discover latest release

Step 3 — Read the manifest

Step 4 — Determine what to apply

What this file has done since we first saw it

Other skills, from other repositories

git-integration

audit-trail

strict-tdd

github-sync

checkpoint-management

issue-tracking