agentmods.dev

mythos codacy.instructions.md

A set of instructions for checking code changes with Codacy, a code-quality analysis service, after files are edited.

In plain words
What is it for?
Use it to analyze each edited file with Codacy's command-line tool and respond when the tool is unavailable.
Why use it?
It helps catch issues in changed files immediately and requires those issues to be addressed before continuing.

Instructions file for GitHub Copilot

2 2d ago A scan 963 tokens copy · 100% MIT
View the source file forbiddenlink/mythos
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/forbiddenlink/mythos/codacy
Clone the repo
git clone --depth 1 https://github.com/forbiddenlink/mythos

Made for: GitHub Copilot.

Per session 963 This file is loaded in full into every session.
When invoked 963 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00963 $0.00963
Opus 5 $0.00481 $0.00481
Sonnet 5 $0.00193 $0.00193
Haiku 4.5 $0.00096 $0.00096

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

Security

Grade A, and why

mythos codacy.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 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.

Origin

This is a copy

100% identical to opilot codacy.instructions.md — 55 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/instructions/codacy.instructions.md · 72 lines

How it starts

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

Codacy Rules

Configuration for AI behavior when interacting with Codacy's MCP Server

CRITICAL: After ANY successful edit_file or reapply operation

  • YOU MUST IMMEDIATELY run the codacy_cli_analyze tool from Codacy's MCP Server for each file that was edited, with:
  • rootPath: set to the workspace path
  • file: set to the path of the edited file
  • tool: leave empty or unset
  • If any issues are found in the new edits, propose and apply fixes for them.

  • NOTE: Failure to follow this rule is considered a critical error.

When you tried to run the codacy_cli_analyze tool and the Codacy CLI is not installed

  • Ask the user 'Codacy CLI is not installed. Would you like me to install it now?'
  • If the user responds with "yes", run the codacy_cli_install tool and then continue with the original task
  • If the user responds with "no", instruct the user that they can disable automatic analysis in the extension settings
  • Wait for the user to respond before proceeding with any other actions

After every response

  • If you made any file edits in this conversation, verify you ran codacy_cli_analyze tool from Codacy's MCP Server

When there are no Codacy MCP Server tools available, or the MCP Server is not reachable

Trying to call a tool that needs a rootPath as a parameter

  • Always use the standard, non-URL-encoded file system path

CRITICAL: Dependencies and Security Checks

  • IMMEDIATELY after ANY of these actions:
  • Running npm/yarn/pnpm install
  • Adding dependencies to package.json
  • Adding requirements to requirements.txt
  • Adding dependencies to pom.xml
  • Adding dependencies to build.gradle
  • Any other package manager operations
  • You MUST run the codacy_cli_analyze tool with:
  • rootPath: set to the workspace path
  • tool: set to "trivy"
  • file: leave empty or unset
  • If any vulnerabilities are found because of the newly added packages:
  • Stop all other operations
  • Propose and apply fixes for the security issues
  • Only continue with the original task after security issues are resolved
  • EXAMPLE:
  • After: npm install react-markdown
  • Do: Run codacy_cli_analyze with trivy
  • Before: Continuing with any other tasks

Read the full file on GitHub · 72 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. yesterday First seen · 72 lines · 963 tokens per session scan A d45a3281ea30

Subscribe to this mod's changes

mythos codacy.instructions.md is an instructions file published in the GitHub repository forbiddenlink/mythos (2 stars, last pushed 2d ago), licensed MIT. It adds 963 tokens to every session, about $0.0048 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to opilot codacy.instructions.md, differing in 55 lines, and is treated as a copy.

Frontendaimythologynextjsstorytelling
Related

Other instructions, from other repositories

core CLAUDE.md

Claude Code instructions for module-federation/core, covering claude task parallelization & development guidelines, core principles, maximum parallelization strategy, universal parallel task patterns and for any codebase task.

module-federation/core · 3,933 tokens

Codex-Skills AGENTS.md

Instructions for TheGoat395/Codex-Skills, covering repository operating notes, required checks, evidence rules and change hygiene.

TheGoat395/Codex-Skills · 294 tokens

souls-directory CLAUDE.md

Instructions for thedaviddias/souls-directory, covering claude.md — project context for ai assistants, project overview, tech stack, critical rules and database is convex.

thedaviddias/souls-directory · 1,675 tokens

nextarter-tailwind AGENTS.md

AGENTS.md instructions for agustinusnathaniel/nextarter-tailwind, covering next.js: always read docs before coding, ai agent guidance: nextarter-tailwind, 1. mental model for agents, implementation delegation and tooling strategy.

agustinusnathaniel/nextarter-tailwind · 1,839 tokens

agentgram CLAUDE.md

Instructions for agentgram/agentgram, covering claude.md — agentgram development guide, project overview, tech stack, monorepo structure and core architecture patterns.

agentgram/agentgram · 4,467 tokens

souls-directory AGENTS.md

Instructions for thedaviddias/souls-directory, covering agents.md, learned user preferences and learned workspace facts.

thedaviddias/souls-directory · 337 tokens