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 yu-iskw/coding-agent-fabric --skill setup-dev-envgit clone --depth 1 https://github.com/yu-iskw/coding-agent-fabricWrote 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/yu-iskw/coding-agent-fabric/setup-dev-env)<a href="https://agentmods.dev/skills/yu-iskw/coding-agent-fabric/setup-dev-env"><img src="https://agentmods.dev/badge/skills/yu-iskw/coding-agent-fabric/setup-dev-env/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/yu-iskw/coding-agent-fabric/setup-dev-env"><img src="https://agentmods.dev/badge/skills/yu-iskw/coding-agent-fabric/setup-dev-env.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.00035 | $0.00573 |
| Opus 5.5 | $0.00014 | $0.00229 |
| Sonnet 5.5 | $0.00007 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
setup-dev-env 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Development Environment
This skill automates the process of setting up the development environment to ensure all tools and dependencies are correctly installed and configured.
Workflow Checklist
- Step 1: Environment Validation
- Check Node.js version against
.node-version - Check for
trunkinstallation
- Check Node.js version against
- Step 2: Dependency Installation
- Run
pnpm install
- Run
- Step 3: Tooling Setup
- Run
trunk installto fetch managed linters and formatters
- Run
Detailed Instructions
1. Environment Validation
Node.js Version
Read the .node-version file in the workspace root. Ensure the current Node.js environment matches this version. If there's a mismatch, inform the user to switch Node versions (e.g., using nvm or fnm).
Trunk CLI
Check if trunk is installed by running trunk --version.
If trunk is not found, advise the user to install it. On macOS, use:
brew install trunk-io
For other platforms, refer to the Trunk installation documentation.
2. Dependency Installation
Run the following command at the workspace root to install all project dependencies. Refer to ../common-references/pnpm-commands.md for more pnpm commands.
pnpm install
3. Tooling Setup
Trunk manages linters and formatters hermetically. Run the following command to ensure all required tools are downloaded and ready. Refer to ../common-references/trunk-commands.md for more Trunk commands.
trunk install
Success Criteria
- All
pnpmdependencies are installed successfully. trunkis installed and all managed tools are initialized.- The Node.js version matches the requirement in
.node-version.
Post-Setup Verification
To ensure the environment is fully operational:
- Invoke Verifier: Run the
verifiersubagent (../../agents/verifier.md). This confirms that the freshly installed dependencies allow for a successful build, pass lint checks, and satisfy all unit tests. - Handle Failure: If the
verifierfails, follow its reporting to resolve environment-specific issues.
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 · 67 lines · 35 tokens per session scan A 7642d67c387b
setup-dev-env is a skill published in the GitHub repository yu-iskw/coding-agent-fabric (1 stars, last pushed 19d ago), licensed Apache-2.0. It adds 35 tokens to every session and 573 once invoked, about $0.0001 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
delegate-coding-agent
Route coding work to another local coding-agent CLI through the llm-provider MCP server. Use when a task benefits from a powerful model for difficult reasoning or a faster, lower-cost model for bounded implementation, tests, investigation, or review.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-cloud-functions
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.
verify
Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
customer-deck-builder
Build tailored customer-facing sales or customer success decks from approved account context and generate the presentation with Gamma through Zapier MCP.
deep-research
Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 8 modes: full research, quick brief, paper review, lit-review, fact-check, three-way literature scan, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question…