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 agentmods add skills/keminghe/common-devx/dot-gitlab-syncnpx skills add KemingHe/common-devx --skill dot-gitlab-syncgit clone --depth 1 https://github.com/KemingHe/common-devxWhat 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 | $0.00064 | $0.01343 |
| Opus 5 | $0.00032 | $0.00672 |
| Sonnet 5 | $0.00013 | $0.00269 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
dot-gitlab-sync 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub-GitLab Template Sync
Synchronize .github/ and .gitlab/ template directories, applying all necessary platform-specific transformations so both directories stay consistent.
Temporary persona: Senior DevOps engineer with expertise in cross-platform template management and CI/CD conventions.
When to Use This Skill
- After editing issue or PR templates in
.github/and needing.gitlab/updated - After editing issue or MR templates in
.gitlab/and needing.github/updated - Auditing both directories for consistency after any template change
- Setting up
.gitlab/templates for the first time from existing.github/templates
Asset Resolution
- Check
./assets/transformation-rules.mdfor the platform transformation reference - If not found, search
**/transformation-rules.mdin repository - If still not found, use the rules documented in this skill's Process section
Process
Step 1: Determine Sync Direction
Ask the user:
- Source: Which directory was just edited? (
.github/or.gitlab/) - Target: Which directory needs updating?
- If unclear, compare file modification timestamps to suggest a direction
Step 2: Inventory Templates
List templates in both directories:
.github/ISSUE_TEMPLATE/vs.gitlab/issue_templates/.github/pull_request_template.mdvs.gitlab/merge_request_templates/merge_request_template.md.github/ISSUE_TEMPLATE/config.yml(GitHub-only, no GitLab equivalent)
Report any templates that exist in source but not in target (new templates to create) or vice versa (orphaned templates to flag).
Step 3: Apply Transformations
For each template, apply the platform-specific transformations from the asset reference:
GitHub to GitLab:
- Remove YAML frontmatter (
name,about,title,labelsfields) - Replace "PR" with "MR" and "pull request" with "merge request" in template body
- Replace "issue/PR number" with "issue/MR number" in Related sections
- Copy to GitLab directory structure (lowercase
issue_templates/,merge_request_templates/) - Skip
config.yml(no GitLab equivalent)
What ships with it
2 files 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.
- 2d ago First seen · 102 lines · 64 tokens per session scan A 083948d3794d
dot-gitlab-sync is a skill published in the GitHub repository KemingHe/common-devx (10 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 1,343 once invoked, about $0.0003 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.
Other skills, from other repositories
developer-marketing-playbook
Complete developer marketing playbook covering DevRel programs, documentation as marketing, API developer experience, community building, and hackathon strategy. For dev-tool founders who need to reach engineers. Follow @WeiYipei on X.
devrel-playbook
Complete Developer Relations playbook — from community building to documentation strategy to event planning. Covers Discord/Slack management, conference speaking, hackathon sponsorship, and measuring DevRel ROI. By @WeiYipei.
doc-bridge-handoff
Resolve Doc Bridge boundaries before changing code.
Technical Documentation Writer
Write developer documentation that developers actually read. API docs, READMEs, architecture guides, and onboarding docs with clarity and structure.
golden-rss
Use when testing the rss golden build.
golden-chat-topics
Use when testing the goldenchattopics golden build.