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.
npx agentmods add instructions/onelogin/onelogin-mcp/copilot-instructionsgit clone --depth 1 https://github.com/onelogin/onelogin-mcpWrote 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/onelogin/onelogin-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/onelogin/onelogin-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/onelogin/onelogin-mcp/copilot-instructions.svg" alt="Measured on agentmods" 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 | $0.02498 | $0.02498 |
| Opus 5 | $0.01249 | $0.01249 |
| Sonnet 5 | $0.00500 | $0.00500 |
| Haiku 4.5 | $0.00250 | $0.00250 |
Grade A, and why
onelogin-mcp copilot-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 4d 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for OneLogin MCP Server
Project Overview
This is a Model Context Protocol (MCP) server that provides comprehensive access to the OneLogin API. It enables Claude Desktop and other MCP clients to manage users, apps, roles, authentication, and security settings through comprehensive tools covering the complete OneLogin API surface.
Technology Stack:
- Runtime: Bun (Node.js compatible)
- Language: JavaScript (ES modules)
- Protocol: Model Context Protocol (MCP) SDK v1.20.1
- API: OneLogin API v1 and v2
Repository Structure
onelogin-mcp/
├── index.js # MCP server entry point
├── setup.js # Interactive credential configuration
├── lib/
│ ├── config.js # Credential management
│ ├── onelogin-api.js # OAuth2 client with token caching
│ └── tools/
│ ├── registry.js # Tool registry and dispatcher
│ └── [28 tool modules] # Individual API category handlers
├── package.json
├── CONTRIBUTING.md # Tool description quality guidelines
├── PROGRESS.md # Implementation tracking
└── README.md # User documentation
Architecture Principles
Tool Module Pattern
Each tool module in lib/tools/ follows this structure:
export const tools = [
{
name: 'tool_name',
description: '[Detailed description following CONTRIBUTING.md guidelines]',
inputSchema: { type: 'object', properties: {...}, required: [...] }
}
];
export const handlers = {
tool_name: async (api, args) => {
// Implementation using OneLogin API client
return await api.get('/api/2/path', args);
}
};
Tool Registration
lib/tools/registry.jsautomatically discovers and registers all tools from imported modules- Tool names use snake_case convention
- Handlers receive validated arguments and authenticated API client
Authentication Flow
- Credentials stored in
~/.config/onelogin-mcp/servers.json - OAuth2 token caching handled by
onelogin-api.js - Multiple environment support via
ONELOGIN_SERVERenvironment variable - Automatic token refresh on expiration
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.
- 4d ago First seen · 314 lines · 2,498 tokens per session scan A 4942952d3720
onelogin-mcp copilot-instructions.md is an instructions file published in the GitHub repository onelogin/onelogin-mcp (5 stars, last pushed 10d ago), licensed MIT. It adds 2,498 tokens to every session, about $0.0125 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.
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).
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.
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.
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).
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.
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.