signaltree rollup-entry-points.instructions.md

signaltree rollup-entry-points.instructions.md is an instructions file for GitHub Copilot from JBorgia/signaltree. It costs 736 tokens per session, scanned A, original, Apache-2.0.

A build instruction for Nx Rollup packages with multiple import entry points. An entry point is a file users can import, such as a package’s main API or a NestJS integration.

In plain words
What is it for?
Use it when configuring additional Rollup entry points in an Nx monorepo, a repository that contains multiple related packages or projects. The fix is to add uniquely named root barrel files that re-export each subpath.
Why use it?
It prevents Rollup from overwriting generated files when several entry points are all named index.ts, which can leave some package imports broken.

Instructions file for GitHub Copilot

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.

agentmods
npx agentmods add instructions/jborgia/signaltree/rollup-entry-points
Clone the repo
git clone --depth 1 https://github.com/JBorgia/signaltree

Made for: GitHub Copilot.

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 signaltree rollup-entry-points.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jborgia/signaltree/rollup-entry-points.svg)](https://agentmods.dev/instructions/jborgia/signaltree/rollup-entry-points)
Your own site
<a href="https://agentmods.dev/instructions/jborgia/signaltree/rollup-entry-points"><img src="https://agentmods.dev/badge/instructions/jborgia/signaltree/rollup-entry-points.svg" alt="Measured on agentmods" height="20"></a>
Per session 736 This file is loaded in full into every session.
When invoked 736 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00736 $0.00736
Opus 5 $0.00368 $0.00368
Sonnet 5 $0.00147 $0.00147
Haiku 4.5 $0.00074 $0.00074

Measured 5d ago against content hash dce8d190fe65, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

signaltree rollup-entry-points.instructions.md 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 5d 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.

.github/instructions/rollup-entry-points.instructions.md · 119 lines

How it starts

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

Nx Rollup additionalEntryPoints - Filename Collision Issue

The Problem

When using @nx/rollup:rollup executor with additionalEntryPoints, if multiple entry points have the same filename (e.g., all named index.ts), Rollup will output them with the same name, causing files to overwrite each other.

Example of the Problem

// project.json - THIS CAUSES PROBLEMS
{
  "build": {
    "executor": "@nx/rollup:rollup",
    "options": {
      "main": "packages/events/src/index.ts",
      "additionalEntryPoints": [
        "packages/events/src/nestjs/index.ts",   // Output: index.esm.js
        "packages/events/src/angular/index.ts",  // Output: index.esm.js (OVERWRITES!)
        "packages/events/src/testing/index.ts"   // Output: index.esm.js (OVERWRITES!)
      ]
    }
  }
}

Result: Only one index.esm.js survives. The other subpaths are broken.

The Solution

Create uniquely-named barrel files at the package root that re-export from the subdirectory:

1. Create Barrel Files

// packages/events/src/nestjs.ts
/**
 * @signaltree/events/nestjs
 * Re-export barrel for NestJS integration.
 */
export * from './nestjs/index';
// packages/events/src/angular.ts
export * from './angular/index';
// packages/events/src/testing.ts
export * from './testing/index';

2. Update project.json

{
  "build": {
    "executor": "@nx/rollup:rollup",
    "options": {
      "main": "packages/events/src/index.ts",
      "additionalEntryPoints": [
        "packages/events/src/nestjs.ts",   // Output: nestjs.esm.js ✓
        "packages/events/src/angular.ts",  // Output: angular.esm.js ✓
        "packages/events/src/testing.ts"   // Output: testing.esm.js ✓
      ]
    }
  }
}

3. Update package.json exports

{
  "exports": {
    ".": {
      "types": "./index.d.ts",
      "import": "./index.esm.js"
    },
    "./nestjs": {
      "types": "./nestjs.d.ts",
      "import": "./nestjs.esm.js"
    },
    "./angular": {
      "types": "./angular.d.ts",
      "import": "./angular.esm.js"
    },
    "./testing": {
      "types": "./testing.d.ts",
      "import": "./testing.esm.js"
    }
  }
}

Read the full file on GitHub · 119 lines

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. 5d ago First seen · 119 lines · 736 tokens per session scan A dce8d190fe65

Subscribe to this mod's changes

signaltree rollup-entry-points.instructions.md is an instructions file published in the GitHub repository JBorgia/signaltree (22 stars, last pushed 14d ago), licensed Apache-2.0. It adds 736 tokens to every session, about $0.0037 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-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 3,733 tokens