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 aiya000/dotfiles --skill sync-labels-from-prs-and-sub-issuesgit clone --depth 1 https://github.com/aiya000/dotfilesWrote 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/aiya000/dotfiles/sync-labels-from-prs-and-sub-issues)<a href="https://agentmods.dev/skills/aiya000/dotfiles/sync-labels-from-prs-and-sub-issues"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/sync-labels-from-prs-and-sub-issues/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/aiya000/dotfiles/sync-labels-from-prs-and-sub-issues"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/sync-labels-from-prs-and-sub-issues.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.00104 | $0.02325 |
| Opus 5 | $0.00052 | $0.01162 |
| Sonnet 5 | $0.00021 | $0.00465 |
| Haiku 4.5 | $0.00010 | $0.00232 |
Grade A, and why
sync-labels-from-prs-and-sub-issues 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 yesterday.
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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRとSub Issuesから領域ラベルを同期
目的
Issueに紐づくPRとSub Issuesの変更ファイルパスから領域ラベルを算出し、対象PR、Sub Issues、親Issueへ同期する。根拠がなくなった領域ラベルは除去する。
算出元は常にPRの変更ファイルパスとし、Issue本文から領域を推測しない。ラベルの書き込み前に差分を提示し、必ずユーザーの明示的な承認を得る。
入力
- Issue番号またはPR番号。
#2685と2685の両形式を受け付ける - 省略時は現在のブランチに紐づくPRを対象とし、その親Issueを辿る
- 対象リポジトリ。省略時は現在のリポジトリを使う
管理対象の領域ラベル
| ラベル | 変更パス条件 |
|---|---|
native-app |
frontend/ios/**、frontend/android/**、*.swift、*.kt、*.java、*.plist、*.pbxproj、*.gradle、frontend/capacitor.config.ts、frontend/resources/** |
frontend |
frontend/**。ただし frontend/ios/**、frontend/android/**、frontend/k8s/** を除く |
edge-node |
backend/edge_node/** |
account-node |
backend/account_node/** |
edge-node と account-node |
backend/common/**、backend/config/**、backend/main.py、backend/migrate.py、backend/Dockerfile*、backend/pyproject.toml、backend/uv.lock、backend/scripts/**、backend/tests/** |
k8s |
frontend/k8s/**、backend/*/k8s/**、**/kustomization.yaml、**/values.yaml |
monthly-review |
knowledge/devin-workflow/reports/**。developer-experience も併せて付与 |
developer-experience |
.devin/**、.agents/**、**/AGENTS.md、knowledge/** |
other-implementation |
.github/** |
documentation |
docs/**、ルートおよび各ディレクトリの README.md |
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.
- yesterday First seen · 138 lines · 104 tokens per session scan A c466830d2cbc
sync-labels-from-prs-and-sub-issues is a skill published in the GitHub repository aiya000/dotfiles (19 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 2,325 once invoked, about $0.0005 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-09-09.
Other skills, from other repositories
autopilot
Carry a well-scoped GitHub issue through the full dev loop autonomously, stopping at a per-run tier boundary (PR-ready, or merge+deploy for small reversible changes).
autopilot-triage
Vet open issues for autonomous resolution and queue the qualifying ones with the autopilot-queued label — the start-of-day "fill the queue" half of the triage → run split.
create-pr
Create a pull request with auto-generated description, issue linking, ROADMAP updates, and PR-metadata validation.
write-ticket-description
Voice guide for writing issue/ticket/task/epic descriptions. Use this skill for ALL issue creation — GitHub issues, Jira tasks, Monday tasks, Linear tasks, and epics. Contains section structure, voice rules, and anti-patterns. Never write ticket descriptions without invoking this skill first.
use-beads
Full reference for the beads task management workflow. Use when working with beads issues, planning multi-step work, or managing task lifecycle.
use-trekker
Full reference for the trekker task management workflow. Use when working with trekker issues, planning multi-step work, or managing task lifecycle.