Borrowing it
Nothing to install: this file belongs to MOBAI547800/abaqus-codex-mcp. 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/MOBAI547800/abaqus-codex-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/MOBAI547800/abaqus-codex-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/mobai547800/abaqus-codex-mcp/agents-md)<a href="https://agentmods.dev/instructions/mobai547800/abaqus-codex-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/mobai547800/abaqus-codex-mcp/agents-md.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.1 | $0.00343 | $0.00343 |
| Opus 5 | $0.00171 | $0.00171 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
abaqus-codex-mcp 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 7d 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.
What it actually says
Repository guidance
Scope
This repository implements a local STDIO MCP server for OpenAI Codex and Abaqus.
Keep Abaqus execution local and constrain every file operation to
ABAQUS_MCP_WORKSPACE_DIR.
Required checks
Before submitting changes:
.\.venv\Scripts\python.exe -m pytest tests -v
For packaging or dependency changes, reinstall into a clean virtual environment
and run the MCP protocol tests in tests/test_cli.py.
Safety rules
- Never add an arbitrary shell execution tool.
- Never use
shell=True. - Validate user-provided paths through
security.validate_path. - Mark tools accurately with MCP read/write/destructive annotations.
- Keep explicit
confirmed=truegates for background submission, synchronous solving, and file deletion. - Keep
run_scriptapproval bound to the current SHA-256 and block high-risk AST findings by default. Never describe this as an OS sandbox. - Keep ODB selectors in JSON payloads consumed by the fixed worker; never insert user strings into Python source.
- Persist job state atomically and prefer
job_idfor nested or duplicate jobs. - Do not claim a live Abaqus result from mocked tests.
- Keep polishing model construction and contact extraction in fixed workers driven by JSON payloads. Never interpolate user values into Python source.
- A polishing calibration is successful only after an independent final job passes G0-G7, including three-force balance and energy/penetration checks.
- The fixed polishing workers require licensed Abaqus and are excluded from ordinary CPython coverage; validate them through the explicit live gate.
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.
- 7d ago First seen · 40 lines · 343 tokens per session scan A a64b5801a5d5
abaqus-codex-mcp AGENTS.md is an instructions file published in the GitHub repository MOBAI547800/abaqus-codex-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 343 tokens to every session, about $0.0017 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
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 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.
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 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).
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.