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-global-kiro-skilsgit 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-global-kiro-skils)<a href="https://agentmods.dev/skills/aiya000/dotfiles/sync-global-kiro-skils"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/sync-global-kiro-skils/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-global-kiro-skils"><img src="https://agentmods.dev/badge/skills/aiya000/dotfiles/sync-global-kiro-skils.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.00076 | $0.02000 |
| Opus 5 | $0.00038 | $0.01000 |
| Sonnet 5 | $0.00015 | $0.00400 |
| Haiku 4.5 | $0.00008 | $0.00200 |
Grade A, and why
sync-global-kiro-skils 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync global Kiro settings
Keep the live global Kiro permissions and their dotfiles template from drifting apart without copying Kiro runtime data or replacing linked Skill trees.
Scope
| Target | HOME, loaded by Kiro | DOTFILES, version-controlled | Expected relation |
|---|---|---|---|
| Skills root | ~/.kiro/skills |
~/.dotfiles/.kiro_global/skills |
HOME is a symlink to DOTFILES; verify only |
| Steering root | ~/.kiro/steering |
~/.dotfiles/.kiro_global/steering |
HOME is a symlink to DOTFILES; verify only |
| Permissions | ~/.kiro/settings/permissions.yaml |
~/.dotfiles/.kiro_global/settings/permissions.yaml |
DOTFILES is a portable template; HOME is a configured copy |
The Skills root contains this Skill itself. Never copy, mirror, replace, or recursively synchronize either Skills directory. When the link is healthy, both paths already refer to one tree.
Expected differences
The permissions files are expected to differ in machine-specific places. These differences are not necessarily drift:
{YOUR-HOME}placeholders in DOTFILES versus the real home path in HOME- Workspace-specific
fs_readandfs_writepaths - Machine-specific executable paths
- Temporary, project-specific, or exact shell permission rules generated during local work
- Comments or quoting differences that do not change the YAML value
Drift is a general rule that should apply across machines but exists on only one side, such as a reusable shell rule, a global Skill permission, or a global capability setting.
Excluded data
Do not synchronize or delete any of the following:
~/.kiro/settings/cli.jsonunless a future version of this Skill explicitly adds a DOTFILES templatefeed_state.json,survey_state.json,argv.json, or.trust-migration.jsonlogs/,sessions/,session-index/,workspace-roots/,extensions/, orpowers/- Workspace-local
.kiro/directories - Any file outside the table in this Skill
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 · 172 lines · 76 tokens per session scan A 49cebcb2d355
sync-global-kiro-skils is a skill published in the GitHub repository aiya000/dotfiles (19 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 2,000 once invoked, about $0.0004 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
use-notion
Reference for using the Notion API via the notion-agent subagent. Use to expore and update Notion workspace content.
restart__pull_request
A pull-request restart workflow for replacing a messy review with a new pull request containing one clean commit and a summary of the earlier discussion.
rescue__pull_request_review
An automated workflow for handling GitHub pull-request review comments, applying requested code changes, committing them, and pushing them back.
submit__pull_request
An automated pull-request submission workflow. A pull request is a request for a code change to be reviewed and merged; this workflow writes its explanation, creates it, watches its automated checks, and fixes failed checks.
write__pull_request
A workflow for writing a pull request description, the explanation attached to a proposed code change for review. It analyses the changes and commit history.
monitor__ci_status
An automated monitor for GitHub Actions, the service that runs checks such as tests after code changes. It watches all checks after a pull request or a push to a pull-request branch and can invoke a failure-recovery process.