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 rahmanef63/si-coder-agent --skill sc-dxgit clone --depth 1 https://github.com/rahmanef63/si-coder-agentWrote 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/rahmanef63/si-coder-agent/sc-dx)<a href="https://agentmods.dev/skills/rahmanef63/si-coder-agent/sc-dx"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-dx/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/rahmanef63/si-coder-agent/sc-dx"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-dx.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.00051 | $0.00758 |
| Opus 5 | $0.00026 | $0.00379 |
| Sonnet 5 | $0.00010 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
sc-dx 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 4d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sc-dx — make the frontend easy to understand, change, debug, and verify
Language
Keep durable instructions in English. Reply in the user's language unless requested otherwise.
DX objective
Minimize four times without sacrificing correctness:
time-to-understand → time-to-change → time-to-debug → time-to-verify.
Inspect first
Before refactoring, identify:
- framework/runtime/package manager,
- source/layout boundaries,
- component and design-system locations,
- state/data ownership,
- CSS/token strategy,
- build/test/lint/typecheck commands,
- local environment requirements,
- generated files and canonical sources,
- ownership or scope constraints.
Do not reorganize a functioning project merely to match a favorite template.
Frontend DX rules
- Canonical source is explicit. Generated copies/artifacts must say how they are regenerated.
- Reuse tokens/components before creating near-duplicates.
- Prefer semantic component APIs over prop soups and boolean combinations that can represent impossible states.
- Keep naming boring and searchable. File/component/action names should reveal purpose.
- Keep layout/style primitives composable; avoid scattered magic numbers and repeated one-off values when a token/variable already exists.
- Separate product state, view state, and transient interaction state when that distinction improves debugging.
- Errors are actionable: state what failed, where, why when known, and the next recovery action.
- Commands are predictable, scriptable, and non-destructive by default.
- Build/test feedback should identify the smallest useful failure boundary.
- Do not hide important side effects behind innocent-looking helpers.
- Document unusual constraints close to the code or canonical project knowledge, not in tribal memory.
- Preserve existing conventions unless changing them measurably improves the repository.
Component contract
For reusable UI components, prefer:
- clear required vs optional inputs,
- controlled/uncontrolled behavior only when needed and documented,
- semantic variants rather than arbitrary style knobs,
- typed/validated events and state transitions,
- accessible defaults,
- testable deterministic behavior,
- escape hatches that are explicit rather than accidental.
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.
- 4d ago First seen · 69 lines · 51 tokens per session scan A 911c4ce96cd8
sc-dx is a skill published in the GitHub repository rahmanef63/si-coder-agent (12 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 758 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-09-07.
Other skills, from other repositories
threejs-performance
A guide for making Three.js and React Three Fiber 3D projects run more smoothly. Three.js is a JavaScript library for displaying 3D graphics in a browser, while React Three Fiber connects it to React.
performance-profiler
Profile and optimize application performance including load times, memory usage, and rendering. Use when debugging slow performance, memory leaks, or optimizing app speed.
error-boundary-creator
Create error boundaries, error handling, and fallback UIs for React applications. Use when implementing error handling, creating fallback components, or setting up error reporting.
swc-plugin-compatibility
Diagnose and fix Lingui SWC plugin compatibility errors with Next.js, Vite, Rspack, or other SWC runtimes. Use when seeing errors like "failed to invoke plugin", "failed to run Wasm plugin transform", "Failed to deserialize program received from host", "Failed to execute SWC plugin", "out of bounds memory access", or…
frontend-bugfix-debugger
Diagnose and fix frontend defects from evidence, including unclear UI/runtime errors, broken routes, styling regressions, and hydration or client issues. Reproduce before editing; exclude planned refactors and backend-only debugging.
cross-platform-error-handling
Design consistent error handling across web, mobile, and React Native—central handlers, user-facing copy, retry, and logging.