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 itaywol/adeptability --skill adept-code-stylegit clone --depth 1 https://github.com/itaywol/adeptabilityWrote 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/itaywol/adeptability/adept-code-style)<a href="https://agentmods.dev/skills/itaywol/adeptability/adept-code-style"><img src="https://agentmods.dev/badge/skills/itaywol/adeptability/adept-code-style/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/itaywol/adeptability/adept-code-style"><img src="https://agentmods.dev/badge/skills/itaywol/adeptability/adept-code-style.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.00053 | $0.00733 |
| Opus 5.5 | $0.00021 | $0.00293 |
| Sonnet 5.5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
adept-code-style 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 1mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
adept code style
Conventions for Go in github.com/itaywol/adeptability. CI enforces formatting and lint;
the rest is reviewed.
Formatting & lint (enforced)
gofmt+goimports— tabs for indentation, grouped imports (stdlib / third-party / local). CI fails on any unformatted file.golangci-lint run(.golangci.yml):errcheck(incl. type assertions),staticcheck,govet,gocritic,revive(every exported symbol needs a doc comment),errorlint,nilerr,bodyclose,prealloc,unconvert,misspell,unused,ineffassign.
Errors
- Always wrap with context and
%w:fmt.Errorf("clone %s: %w", url, err). - Compare with
errors.Isagainst the sentinels inpkg/adept/errors.go(ErrSkillNotFound,ErrMergeConflict,ErrBudgetOverflow, …). Never match on error strings. Need a new category? Add a sentinel there. errcheckis strict — handle or explicitly_ =an ignored error, and say why if it isn't obvious. Don't drop an error that loses data.
Structure
- Composition root, no globals. Concrete implementations are wired behind interfaces into
*Depsininternal/cli/deps.go. No package-level mutable state, noinit()side effects. Take dependencies as parameters so code is testable with fakes/mocks. pkg/adeptis types-only. Keep it dependency-light and stable; behavior lives ininternal/. (Example:SkillIDPatternis a string inpkg/adept, compiled ininternal/canonical— don't add aregexpimport topkg/adept.)- Doc comments are full sentences starting with the symbol name (
// NewRoot builds …).
Readability
- Small, single-purpose functions; prefer early returns over deep nesting.
- Name things for what they are; avoid one-letter names outside tight loops/receivers.
- No magic numbers/strings — name on-disk paths and limits as constants (see
pkg/adept/constants.go). - Comments explain why, not what. Keep them in sync with the code — a stale comment is a bug.
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.
- 1mo ago First seen · 59 lines · 53 tokens per session scan A c12bd1e2940a
adept-code-style is a skill published in the GitHub repository itaywol/adeptability (9 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 733 once invoked, about $0.0002 per session on Opus 5.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
copilot-sdk
Build applications powered by GitHub Copilot using the Copilot SDK — session management, custom tools, streaming, hooks, MCP servers, BYOK, deployment patterns.
concurrency-patterns-go
Apply safe, idiomatic Go concurrency patterns with goroutines and channels. Use when the user works with goroutines, channels, sync primitives, context cancellation, worker pools, fan-in/fan-out, select statements, or asks about concurrent Go programming and avoiding race conditions.
error-handling-go
Implement robust Go error handling with wrapping, sentinel errors, and custom types. Use when the user handles errors in Go, creates custom error types, wraps errors with fmt.Errorf and %w, uses errors.Is/As, or asks about Go error best practices and error propagation strategies.
idiomatic-go
Write clean, idiomatic Go following community conventions and effective patterns. Use when the user writes Go code, designs packages, defines interfaces, uses struct embedding, writes receiver methods, organizes Go projects, or asks about Go best practices and conventions.
go-expert
Use this skill when writing or reviewing Go code. Covers Go idioms, concurrency patterns, error handling, project structure, testing, benchmarks, and production-grade Go standards.
hns-moaiadk-best-practices
Every change must pass all five dimensions before completion.