Sashiko is an automated code-review system specialized for proposed Linux kernel changes. Kernel maintainers and developers use it to inspect patches from mailing lists or local Git repositories with Linux-specific review instructions and language models. The catalogue add-ons provide its agent workflow.
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 sashiko-dev/sashiko --skill sashiko-featuregit clone --depth 1 https://github.com/sashiko-dev/sashikoWrote 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/sashiko-dev/sashiko/sashiko-feature)<a href="https://agentmods.dev/skills/sashiko-dev/sashiko/sashiko-feature"><img src="https://agentmods.dev/badge/skills/sashiko-dev/sashiko/sashiko-feature.svg" alt="Measured on agentmods" 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.00051 | $0.00445 |
| Opus 5 | $0.00026 | $0.00222 |
| Sonnet 5 | $0.00010 | $0.00089 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
sashiko-feature 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 7d 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.
What it actually says
Sashiko Feature Creation Skill
Core Workflow
Follow this structured process for every feature implementation request:
1. Analysis & Discovery
- Read Baseline: Read
GEMINI.mdto identify project-wide constraints, coding standards, and mandatory practices. - Detect Design Docs: Search the
designs/directory for documents relevant to the feature request. If multiple docs seem relevant or none are found, ask the user for clarification. - Investigate Codebase: Invoke the
codebase_investigatoron the modules likely to be affected. Determine:- Existing paradigms and data structures.
- Integration points.
- Potential impacts on other system components.
2. Planning
- Propose a step-by-step implementation plan.
- Commit Strategy: Plan to split the work into small, logical, and self-sufficient commits.
- Principles Alignment: Reference references/principles.md to ensure the proposed design adheres to SOLID/DRY principles in a Rust context.
3. Implementation & Iterative Validation
- Execute the plan one step at a time.
- Standard Adherence: Adhere strictly to idiomatic Rust (v1.90 compatibility) and the rules in
GEMINI.md. - Continuous Checking: After every iteration of code changes:
- Run
make lintfor formatting and clippy checks. - Run
make testfor unit testing. - Run
make check-prbefore completing a task to ensure all CI-level checks pass.
- Run
- Sign-off: All commits must be signed-off (
git commit -s).
4. Final Review
- Summarize the changes against the original request.
- Verify that no temporary logs or files are left behind.
- Ensure the final state of the repository is clean.
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.
- 7d ago First seen · 36 lines · 51 tokens per session scan A 4a5123e8d890
sashiko-feature is a skill published in the GitHub repository sashiko-dev/sashiko (1,212 stars, last pushed yesterday), licensed Apache-2.0. It adds 51 tokens to every session and 445 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-30.
Other skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
omh-rust
This is a Hermes-native rust workflow skill.
bevy-ecs
Structure a Bevy app around its Entity Component System: build the App with plugins, define Component/Resource types, write systems with Query/Res/Commands, filter and order systems, and use the Time resource for frame-rate-independent motion. Use when building or debugging a Bevy game in Rust — when the user mentions…
rust-project
Modern Rust project architecture guide for 2025. Use when creating Rust projects (CLI, web services, libraries). Covers workspace structure, error handling, async patterns, and idiomatic Rust best practices.
gcs-rust-download-object-api
Fix "DownloadObjectRequest not found" error in google-cloud-storage Rust crate. Use when: (1) Trying to download objects from GCS using the Rust SDK, (2) Looking for a download request type in http::objects::download module, (3) Compile error about missing type. The downloadobject method uses GetObjectRequest from the…
azure-keyvault-secrets-rust
Client library for Azure Key Vault Secrets — secure storage for passwords, API keys, and other secrets.