nexus AGENTS.md

Project instructions for Claudesidian MCP, an Obsidian community plugin that connects AI tools to notes in an Obsidian vault.

In plain words
What is it for?
Use them when changing the plugin lifecycle, agents, services, database code, commands, or CSS.
Why use it?
They explain the plugin's structure, supported technologies, lifecycle rules, and styling requirements so edits remain compatible and maintainable.

Instructions file for CodexOpenCode

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/profsynapse/nexus/agents-md
Clone the repo
git clone --depth 1 https://github.com/ProfSynapse/nexus

Made for: Codex, OpenCode.

Per session 7,564 This file is loaded in full into every session.
When invoked 7,564 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.07564 $0.07564
Opus 5 $0.03782 $0.03782
Sonnet 5 $0.01513 $0.01513
Haiku 4.5 $0.00756 $0.00756

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

Security

Grade A, and why

nexus AGENTS.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 2d 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.

AGENTS.md · 654 lines

How it starts

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

Codex Context Document

Last Updated: 2026-04-04

Project Overview

  • Name: Claudesidian MCP
  • Version: 5.11.1
  • Type: Obsidian Community Plugin
  • Purpose: MCP integration for Obsidian with AI-powered vault operations
  • Architecture: Agent-Tool pattern with domain-driven design
  • Stack: TypeScript, Node.js, Obsidian Plugin API, MCP SDK

Obsidian Plugin Development Guidelines

This is an Obsidian community plugin that must follow official Plugin Guidelines. All code changes must adhere to these best practices.

Plugin Lifecycle

// Plugins extend the Plugin base class
export default class MyPlugin extends Plugin {
    async onload() {
        // Initialize UI, register commands, set up events
        // Use registration methods for auto-cleanup
    }

    async onunload() {
        // Clean up resources (most handled automatically)
    }
}

Key lifecycle rules:

  • All registration methods (registerEvent, addCommand, registerView, registerInterval) auto-cleanup on unload
  • Never store view references in the plugin instance (causes memory leaks)
  • Use this.app.workspace.onLayoutReady() to defer startup operations

Styling - ALL STYLES IN styles.css

CRITICAL: All styles must be defined in styles.css, never inline in TypeScript/JavaScript.

// ❌ NEVER do this
element.style.color = 'white';
element.style.backgroundColor = 'red';
element.style.display = 'flex';

// ✅ ALWAYS do this
element.addClass('my-plugin-element');
/* In styles.css - use CSS variables for theme compatibility */
.my-plugin-element {
    color: var(--text-normal);
    background-color: var(--background-primary);
    display: flex;
}

Required CSS Variables (never hardcode colors):

Variable Purpose
--text-normal, --text-muted, --text-faint Text colors
--text-accent Interactive/link text
--background-primary, --background-secondary Background colors
--background-modifier-border Borders
--background-modifier-error Error states
--interactive-accent, --interactive-accent-hover Buttons/interactive
--radius-s, --radius-m, --radius-l Border radius

Read the full file on GitHub · 654 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. 2d ago First seen · 654 lines · 7,564 tokens per session scan A 059337d4f37b

Subscribe to this mod's changes

nexus AGENTS.md is an instructions file published in the GitHub repository ProfSynapse/nexus (154 stars, last pushed 2d ago), licensed MIT. It adds 7,564 tokens to every session, about $0.0378 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

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

buildNext

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

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 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

spec-kit 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,040 tokens

langchain 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,345 tokens