add-global-mode-target

A repository-specific procedure for adding global-mode support to one existing Agentsmesh target. Global mode means storing or loading an agent's configuration in a user-wide location instead of only inside one project.

In plain words
What is it for?
Use it when extending one existing target after its native global paths and behaviour are documented. It guides contract checks, implementation touchpoints, strict tests, documentation updates, and final verification.
Why use it?
It prevents developers from guessing where a target keeps global files or missing the code paths needed to generate, import, rewrite, test, and document them. It is intended for targets that already have documented global behaviour.

Skill for Claude CodeCodex

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 skills/samplexbro/agentsmesh/add-global-mode-target
Any agent
npx skills add sampleXbro/agentsmesh --skill add-global-mode-target
Clone the repo
git clone --depth 1 https://github.com/sampleXbro/agentsmesh

Made for: Claude Code, Codex.

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,360 The whole file, excluding the scripts and references it only reads on demand.
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.00061 $0.01360
Opus 5 $0.00030 $0.00680
Sonnet 5 $0.00012 $0.00272
Haiku 4.5 $0.00006 $0.00136

Measured yesterday against content hash 4435f7366b77, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

add-global-mode-target 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 yesterday.

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/skills/add-global-mode-target/SKILL.md · 131 lines

How it starts

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

Purpose

Add Global Mode Target

Use this skill when the task is to add global mode support for one existing target after you have a target-specific document that describes the native global file paths and behavior.

Read ./references/global-mode-target-checklist.md before editing code. Treat it as the minimum implementation and QA checklist.

When To Use

  • The target already exists in src/targets/<target>/
  • You have a target doc with native global paths or global behavior
  • The repository-wide global-mode foundation already exists (init|install|generate|import|diff|lint|watch|check|merge|matrix --global)
  • The work is scoped to one target at a time

Do Not Use This Skill For

  • Adding a brand-new target from scratch
  • Defining the shared global-mode architecture for the first time
  • Guessing a target's global behavior without a concrete doc or official source

Use add-agent-target for new targets. Use this skill only for the per-target global-mode pass.

Non-Negotiable Rules

MUST

  • Start from the target doc and verify it against the live target implementation.
  • Treat current code as the source of truth for project-mode behavior; preserve it unless the target doc requires a change.
  • Write failing tests first for every new global-mode behavior.
  • Keep the change target-scoped. Do not scatter new target-specific branches through shared code if descriptor metadata can carry the behavior.
  • Add or update descriptor.global and keep project/global layout semantics explicit.
  • Verify link rewriting and import normalization for the target's global paths, not just generation paths.
  • Test unsupported global features explicitly. If the target has no meaningful native global support, encode that and test the skip/warning behavior.
  • Update docs if the supported-tools matrix, README, or global-mode docs change.
  • Run the full verification stack before claiming completion.

MUST NOT

  • Do not infer global paths from project-mode paths.
  • Do not hardcode the target's global paths in shared cleanup or reference code when descriptor metadata can own them.
  • Do not stop at “files generate”; global import, reference rewriting, and stale cleanup must also be checked when applicable.
  • Do not silently mark a target as globally supported if only a subset of features work natively.

Read the full file on GitHub · 131 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. yesterday First seen · 131 lines · 61 tokens per session scan A 4435f7366b77

Subscribe to this mod's changes

add-global-mode-target is a skill published in the GitHub repository sampleXbro/agentsmesh (23 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 1,360 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-30.

Related

Other skills, from other repositories

auth-web-cloudbase

CloudBase Web Authentication Quick Guide for frontend integration after auth-tool has already been checked. Provides concise and practical Web authentication solutions with multiple login methods and complete user management.

TencentCloudBase/CloudBase-AI-Toolkit · 38 tokens

fix-codesign-error

Slash command that inspects a macOS signing or entitlement failure and explains the minimum fix path. Invoke explicitly with /fix-codesign-error — this skill never self-triggers.

robinebers/openusage · 42 tokens

browse-and-evaluate

Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.

MoizIbnYousaf/Ai-Agent-Skills · 43 tokens

specflow-use

To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.

griddynamics/rosetta · 27 tokens

loop-engineering

Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).

huytieu/COG-second-brain · 63 tokens

telnyx-messaging-hosted-curl

Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.

team-telnyx/ai · 45 tokens