Jarvis Registry is a gateway that connects AI copilots and autonomous agents to enterprise tools through the Model Context Protocol and agent-to-agent communication. Organizations use it to manage identity, permissions, tool discovery, orchestration, logging, and observability, while the catalogue entries support agent workflows with it.
Borrowing it
Nothing to install: this file belongs to ascending-llc/jarvis-registry. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ascending-llc/jarvis-registry/main/AGENTS.mdgit clone --depth 1 https://github.com/ascending-llc/jarvis-registryWrote 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.
[](https://agentmods.dev/instructions/ascending-llc/jarvis-registry/agents-md)<a href="https://agentmods.dev/instructions/ascending-llc/jarvis-registry/agents-md"><img src="https://agentmods.dev/badge/instructions/ascending-llc/jarvis-registry/agents-md/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.
<a href="https://agentmods.dev/instructions/ascending-llc/jarvis-registry/agents-md"><img src="https://agentmods.dev/badge/instructions/ascending-llc/jarvis-registry/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.02693 | $0.02693 |
| Opus 5.5 | $0.01077 | $0.01077 |
| Sonnet 5.5 | $0.00539 | $0.00539 |
| Haiku 4.5 | $0.00269 | $0.00269 |
Grade A, and why
jarvis-registry 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 21d 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jarvis Registry — Agent Guide
Python 3.12 monorepo (FastAPI, Beanie on MongoDB, Weaviate, Redis) plus a React frontend. All Python workspaces are managed by uv from the root pyproject.toml.
| Workspace | Depends on | Purpose |
|---|---|---|
registry/ |
registry-pkgs |
Main backend: REST API and MCP proxy |
auth-server/ |
registry-pkgs |
OAuth2/OIDC auth server (Entra ID, Google) |
workflow-worker/ |
registry-pkgs |
Workflow scheduler and executor |
registry-pkgs/ |
— | Shared Beanie models, DB/Redis clients, vector search, telemetry, migrations |
frontend/ |
— | SPA (Vite, React 18, TailwindCSS, Biome) |
Design and Review Discussions
When reviewing a plan, spec or change with the developer, first ask which mode they want (unless the command or skill in use defines its own format):
- BIG CHANGE: work through the review stages one at a time.
- SMALL CHANGE: raise only the single most important question per stage.
Review stages
Go through these in order. Skip a stage that has no issues, and say that you skipped it.
- Architecture: component boundaries, coupling, data flow, scaling and single points of failure, security (auth, data access, API boundaries).
- Code quality: module structure, duplication, error handling and missing edge cases, technical debt, over- or under-engineering.
- Tests: coverage gaps, assertion strength, untested edge cases and failure paths.
- Performance: N+1 queries and database access patterns, memory use, caching, expensive code paths.
After each stage, stop and wait for the developer's answers before starting the next one. Don't assume priorities on timeline or scale.
Raising issues
- Rank issues by severity. Discuss the top ones in full and list the rest in one line each.
- For each issue, describe the problem concretely with
file:linereferences, then give 2–3 options, including "do nothing" where reasonable. For each option, state effort, risk, impact on other code and maintenance burden. - Put the recommended option first and explain why. When options are close, prefer the one that removes duplication, handles more edge cases, and is explicit rather than clever.
- Number issues and letter options so the developer can answer "2B". Format each issue like this:
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.
- 21d ago Changed · -308 lines · -2,955 tokens per session 9b526061be26
- 22d ago Changed · +21 lines · +716 tokens per session 0df103f6df83
- 1mo ago Changed · +1 tokens per session b8716f7688a3
- 1mo ago Changed · +6 lines · +137 tokens per session 50208d9cd156
- 1mo ago First seen · 427 lines · 4,794 tokens per session scan A a14051bd8add
jarvis-registry AGENTS.md is an instructions file published in the GitHub repository ascending-llc/jarvis-registry (3,704 stars, last pushed today), licensed Apache-2.0. It adds 2,693 tokens to every session, about $0.0108 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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.