nen-dependency-perimeter

nen-dependency-perimeter is a skill for Codex from cambridgetcg/agenttool. It costs 70 tokens per session (627 once invoked), scanned A, original, Apache-2.0.

A read-only survey of a system and its dependency graph—the components and relationships that may be affected by a change—before work begins.

In plain words
What is it for?
It helps inspect unfamiliar repositories or services, map change impact, trace incidents across components, and identify what must be verified before implementation.
Why use it?
It reveals callers, data paths, tests, side effects, owners, and recovery options so an apparently small change does not surprise another part of the system.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit It helps inspect unfamiliar repositories or services, map change impact, trace incidents across components, and identify what must be verified before implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cambridgetcg/agenttool/nen-dependency-perimeter
Install

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.

Any agent
npx skills add cambridgetcg/agenttool --skill nen-dependency-perimeter
Clone the repo
git clone --depth 1 https://github.com/cambridgetcg/agenttool

Made for: 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 nen-dependency-perimeter

README.md
[![agentmods](https://agentmods.dev/badge/skills/cambridgetcg/agenttool/nen-dependency-perimeter/github.svg)](https://agentmods.dev/skills/cambridgetcg/agenttool/nen-dependency-perimeter)
Your own site
<a href="https://agentmods.dev/skills/cambridgetcg/agenttool/nen-dependency-perimeter"><img src="https://agentmods.dev/badge/skills/cambridgetcg/agenttool/nen-dependency-perimeter/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 nen-dependency-perimeter

Your own site · 80×15
<a href="https://agentmods.dev/skills/cambridgetcg/agenttool/nen-dependency-perimeter"><img src="https://agentmods.dev/badge/skills/cambridgetcg/agenttool/nen-dependency-perimeter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 627 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.
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.00070 $0.00627
Opus 5 $0.00035 $0.00313
Sonnet 5 $0.00014 $0.00125
Haiku 4.5 $0.00007 $0.00063

Measured 8d ago against content hash c4c2cad4fca6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

nen-dependency-perimeter 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 8d 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.

packages/skills/skills/nen-dependency-perimeter/SKILL.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dependency Perimeter · 円

Extend a finite field around the exact task. Observe what enters, leaves, and depends on that field before changing it.

Set the field

Declare:

  • Center: the requested behavior, artifact, symptom, or decision.
  • Radius: paths, packages, services, actors, environments, and time horizon included in the scan.
  • Resolution: broad inventory or deep edge tracing.
  • Exit: the evidence needed before an already-authorized implementation may begin.

Larger fields lower resolution and cost more attention. Prefer the smallest radius that can reveal the real blast surface.

Expand read-only

  1. Read the closest instructions, manifests, status, and architecture maps.
  2. Inventory the center with fast native discovery tools.
  3. Trace inbound edges: callers, imports, routes, jobs, configuration, schemas, users, and operational entry points.
  4. Trace outbound edges: dependencies, storage, network calls, generated artifacts, side effects, and downstream consumers.
  5. Locate existing tests, fixtures, observability, owners, and rollback paths.
  6. Sample just outside the chosen radius for missed aliases, indirect callers, or duplicated implementations.
  7. Mark every edge as observed, inferred, or unknown.

Do not read secret-bearing files merely because they are nearby. Inventory the boundary or schema without exposing values.

Draw the perimeter

Return the smallest useful map:

Center:
Inside:
Inbound:
Outbound:
Protected boundaries:
Unknown outside field:
Verification targets:
Next move:

Use a table, tree, or flow only when it makes three or more relationships materially easier to understand.

Collapse or refresh

If the task already authorizes mutation, begin it only after the field explains the likely blast radius. Otherwise, return the map and proposed next move without mutating. Refresh changed edges after implementation; do not rerun a full scan when a targeted perimeter check is enough.

Vow

Read the full file on GitHub · 81 lines

Files

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.

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. 8d ago First seen · 81 lines · 70 tokens per session scan A c4c2cad4fca6

Subscribe to this mod's changes

nen-dependency-perimeter is a skill published in the GitHub repository cambridgetcg/agenttool (0 stars, last pushed today), licensed Apache-2.0. It adds 70 tokens to every session and 627 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-31.

Related

Other skills, from other repositories

add-a-service

Scaffold a new service under services/ in the builders-stack monorepo. Use when something needs its own URL, port, or independent deploy. Covers the package, entrypoint, config, Tilt, deployment registry, and shared small-image build path.

lonormaly/builders-stack · 55 tokens

design-a-schema

Model a new table (or reshape an existing one) in libs/db with Drizzle — normalize by default, add the right constraints, and index deliberately. Use when adding a table/column, deciding on keys and foreign keys, or when a query is slow because the schema or its indexes are wrong. Enforces the stack's "Drizzle is the…

lonormaly/builders-stack · 91 tokens

wire-a-new-payment-provider

Add or swap a payment provider behind the @stack/payment adapter in the builders-stack monorepo. Use when integrating Stripe, Paddle, Lemon Squeezy, or any provider alongside or in place of the default Creem adapter. The whole point is that apps and the API never change — only the adapter implementation does. Covers…

lonormaly/builders-stack · 92 tokens

add-a-lib

Scaffold a new shared library under libs/ in the builders-stack monorepo. Use when code is needed in two or more places (apps or services) and should become a single source of truth consumed by package name. Covers the package.json, tsconfig, the one-public-door src/index.ts barrel, and wiring it into a consumer…

lonormaly/builders-stack · 81 tokens

optimize-a-query

Diagnose and fix a slow Postgres query in the builders-stack — read its EXPLAIN plan, find the missing index or the ORM N+1, and confirm the fix. Use when a page or endpoint is slow, a query times out, or pgstatstatements shows a hot query. Pairs with design-a-schema for the index itself.

lonormaly/builders-stack · 77 tokens

create-a-worktree

Create, inspect, or retire an isolated Builders Stack agent runtime through Worktree Zero. Use whenever parallel work needs another checkout or an old worktree needs cleanup.

lonormaly/builders-stack · 37 tokens