MCamnerMCamner/mq-image-analyze/AGENTS.md

mq-image-analyze

AGENTS.md1 starsChanged 22 days agoMITView on GitHub

This repo is part of the MQ stack. These instructions add MQ memory read-order rules. They do not replace repo-specific build, test, safety, or release instructions. Default local vault path: $MQ_OBSIDIAN_DIR If MQ_OBSIDIAN_DIR is set, prefer that value. For work related to mq-image-analyze: Stop reading as soon as the task is grounded. mqobsidian is durable memory, not live runtime truth. If the task depends on current code behavior, tests, contracts, CLI behavior, or runtime state, verify in this repo before…

Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cli-maintainerSkill
- docs-maintainerSkill
- image-quality-auditSkill
- json-contract-maintainerSkill
- mcp-tools-maintainerSkill
- model-setup-maintainerSkill
- release-readinessSkill
- repo-awareSkill
- reverse-promptSkill
- screenshot-ui-reviewSkill
- vision-regression-evalSkill
- visual-architecture-analysisSkill
- visual-reasoningSkill
- web-ui-maintainerSkill

The file

Show its rules and text

We split this AGENTS.md into the rules it gives an agent

15 rules. About 1 is common, 10 are distinctive, and 4 are very specific to this project.

≈1
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Default local vault path:
line 10
Very specific:
If MQ_OBSIDIAN_DIR is set, prefer that value.
line 14
Very specific:
Read .mq/context/task-pack.md if it exists and matches the task.
line 20
Very specific:
Read $MQ_OBSIDIAN_DIR/memory/learn/agent/mq-image-analyze.md if it exists.
line 21
Distinctive:
Read individual pattern notes only if the compressed notes are insufficient.
line 25
Distinctive:
Stop reading as soon as the task is grounded.
line 27
Distinctive:
Prefer task packs and agent views over full notes.
line 31
Distinctive:
Prefer hot/index over pattern notes.
line 32
Distinctive:
Do not scan the whole vault by default.
line 33
Distinctive:
Do not open multiple pattern notes unless clearly needed.
line 34
Distinctive:
If the task depends on current code behavior, tests, contracts, CLI behavior, or runtime state, verify in this repo before making claims.
line 41
Distinctive:
When creating notes, summaries, or exports:
line 46
Distinctive:
prefer links over duplicated prose
line 51
Common:
Do not store or copy secrets, tokens, internal hostnames, raw enterprise logs, or machine-specific private paths.
line 54
Very specific:
If mqobsidian is missing, stale, or too weak for the task, say so and verify in the repo.
line 59

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

AGENTS.md

Agent Instructions For mq-image-analyze

This repo is part of the MQ stack.

These instructions add MQ memory read-order rules. They do not replace repo-specific build, test, safety, or release instructions.

mqobsidian Location

Default local vault path:

$MQ_OBSIDIAN_DIR

If MQ_OBSIDIAN_DIR is set, prefer that value.

Read Order

For work related to mq-image-analyze:

Read .mq/context/task-pack.md if it exists and matches the task.
Read $MQ_OBSIDIAN_DIR/memory/learn/agent/mq-image-analyze.md if it exists.
Read $MQ_OBSIDIAN_DIR/systems/mq-image-analyze/hot.md if it exists.
Read $MQ_OBSIDIAN_DIR/systems/mq-image-analyze/index.md if it exists.
Read $MQ_OBSIDIAN_DIR/memory/learn/repos/mq-image-analyze.md if it exists.
Read individual pattern notes only if the compressed notes are insufficient.

Stop reading as soon as the task is grounded.

Low-Token Rules

Prefer task packs and agent views over full notes.
Prefer hot/index over pattern notes.
Do not scan the whole vault by default.
Do not open multiple pattern notes unless clearly needed.
Summarize instead of replaying long note bodies.

Source-Of-Truth Rule

mqobsidian is durable memory, not live runtime truth.

If the task depends on current code behavior, tests, contracts, CLI behavior, or runtime state, verify in this repo before making claims.

Writing Rules

When creating notes, summaries, or exports:

separate facts, interpretation, and recommendation
keep outputs compact
preserve timestamps and provenance when relevant
prefer links over duplicated prose
avoid raw dumps

Do not store or copy secrets, tokens, internal hostnames, raw enterprise logs, or machine-specific private paths.

Fallback Rule

If mqobsidian is missing, stale, or too weak for the task, say so and verify in the repo. Do not invent continuity.

AGENTS.md — Governor (mansys/mcamner)

Kommunikation

Svara på svenska om inget annat sägs. Kort och direkt. Ingen hype, inga superlativ.
Ärlig bedömning före artighet. Säg "det här är en dålig idé" när det är det, med skäl.
Osäkerhet: säg "kan inte bekräfta" istället för att gissa. Hitta aldrig på källor, siffror eller API:er.

Kod

Kirurgiska ändringar. Rör inte kod utanför uppgiften. Ingen "passade på att refaktorera".
Inga onödiga abstraktioner. Enklaste lösning som håller.
Redovisa antaganden explicit innan implementation. Definiera verifierbart framgångskriterium.
Verifiera innan du deklarerar klart: kör testet, läs outputen, visa beviset.
TDD vid features och bugfixar där det är rimligt: test först.
Läs faktiska filer i repot istället för att gissa struktur.

Arbetssätt

Kör vidare på självklara nästa steg utan att fråga. Fråga endast vid destruktiva operationer (delete, force-push, prod).
Vid felsökning: reproducera → isolera → diagnostisera → fixa. Inte "prova det här och se".
En fråga i taget om förtydligande behövs, och bara om svaret inte redan finns i kontexten.

Miljö

macOS: MQ-stacken. mq-mcp är MCP-servern (hal_repo_report, read_repo_file, run_mqlaunch_doctor, record_learning). Bridget är agenten (bridge.py, bridget_context.py). Repon: mq-mcp, mq-agent, mq-hal, macos-scripts, mqobsidian.
Windows (Region Stockholm): PowerShell-svit med mongo-prefix (mongostart, mongoApps, mongoSys, mongoKommand, loggMongo). GPO-begränsad miljö — räkna med workarounds.
Fedora-testmaskin (Dell Latitude 5290): Fish/bash.
IT-domän: IGEL OS 12, UMS, Citrix CVAD, Intune/Entra ID. Svensk offentlig sektor/vård — säkerhet och spårbarhet väger tungt.

Konventioner

Namnprefix: mq- (macOS), mongo- (Windows).
Estetik: JetBrains Mono, amber/dark terminal, HAL 9000/Amiga-tema.
Dokumentation ofta bilingualt SV/EN.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free