executor: Skill for Claude Code

.agents/skills/wrdn-package-boundaries/SKILL.md

wrdn-package-boundaries is a skill for Claude Code, Codex from UsefulSoftwareCo/executor. It costs 24 tokens per session (155 once invoked), scanned A, original, MIT.

A code-review and fixing guide for keeping packages in a workspace separate. A workspace is a repository containing multiple related packages or applications, and package boundaries define what each one may expose to the others.

In plain words
What is it for?
Use it when lint reports a relative import crossing package roots. Replace it with the package name, or add the smallest necessary public export.
Why use it?
It prevents code from reaching into another package's private files through fragile relative paths. It keeps cross-package imports tied to the target package's public interface.

Skill for Claude CodeCodex

Written for Claude Code: allowed-tools in frontmatter. Also seen: installed under .agents/ (shared by several agents).

This is UsefulSoftwareCo/executor's own configuration. It tells Claude Code and Codex how to work on executor itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything executor configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { createExecutor } from "../../../core/sdk/src";.

About the project

Executor is a shared integration layer that lets AI agents use tools from MCP servers, OpenAPI specifications, GraphQL APIs, and custom JavaScript functions through one catalog. It centralizes credentials and per-tool access policies so MCP-compatible agents can reuse the same integrations.

UsefulSoftwareCo/executor · 4,297 stars · on GitHub · executor.sh

Reuse

Borrowing it

Nothing to install: this file belongs to UsefulSoftwareCo/executor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/UsefulSoftwareCo/executor/main/.agents/skills/wrdn-package-boundaries/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/UsefulSoftwareCo/executor

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for wrdn-package-boundaries

README.md
[![agentmods](https://agentmods.dev/badge/skills/usefulsoftwareco/executor/wrdn-package-boundaries/github.svg)](https://agentmods.dev/skills/usefulsoftwareco/executor/wrdn-package-boundaries)
Your own site
<a href="https://agentmods.dev/skills/usefulsoftwareco/executor/wrdn-package-boundaries"><img src="https://agentmods.dev/badge/skills/usefulsoftwareco/executor/wrdn-package-boundaries/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.

agentmods 80×15 button for wrdn-package-boundaries

Your own site · 80×15
<a href="https://agentmods.dev/skills/usefulsoftwareco/executor/wrdn-package-boundaries"><img src="https://agentmods.dev/badge/skills/usefulsoftwareco/executor/wrdn-package-boundaries.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 155 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00155
Opus 5.5 $0.00010 $0.00062
Sonnet 5.5 $0.00005 $0.00031
Haiku 4.5 $0.00002 $0.00015

Measured 2mo ago against content hash a8bace6db146, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wrdn-package-boundaries 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 2mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/skills/wrdn-package-boundaries/SKILL.md · 27 lines

What it actually says

Workspace packages should import each other through package exports, not relative paths.

Fix Shape

  • Replace cross-package relative imports with the target package name.
  • If the needed module is not exported, add the smallest package export that matches the package's public surface.
  • Keep relative imports only within the same package root.
  • Do not reach into another package's private source tree from an app or package.

Good

import { createExecutor } from "@executor-js/sdk";

Bad

import { createExecutor } from "../../../core/sdk/src";
Changes

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.

  1. 2mo ago First seen · 27 lines · 24 tokens per session scan A a8bace6db146

Subscribe to this mod's changes

wrdn-package-boundaries is a skill published in the GitHub repository UsefulSoftwareCo/executor (4,297 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 155 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-30.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens