simplenote-mcp-server / helm
AGENTS.md21 starsChanged 24 days agoMITView on GitHub
Helm chart for deploying simplenote-mcp-server to Kubernetes (helm/simplenote-mcp-server/).
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,700 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/skills/AGENTS.mdAGENTS.md
- .github/workflows/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- dependabotSkill
- docs-sync-auditSkill
- github-actions-hardeningSkill
- mcp-implementation-security-reviewSkill
- mcp-release-qaSkill
- mcp-security-auditSkill
- pytest-coverageSkill
- security-reviewSkill
- test-gap-auditSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 17
No real credentials in values.yaml or any committed values file — secret.yaml expects .Values.simplenote.password to be supplied at install …
≈ “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.
Files
helm/
Purpose
Helm chart for deploying simplenote-mcp-server to Kubernetes (helm/simplenote-mcp-server/).
Ownership
Chart.yaml— chart metadata;versionandappVersionmust track the project version (see Local Contracts).values.yaml— defaults (replica count, image repo/tag, security context, resources).templates/—deployment.yaml,service.yaml,serviceaccount.yaml,configmap.yaml,secret.yaml(rendersSIMPLENOTE_PASSWORDfrom.Values.simplenote.password, base64-encoded — never hardcode a real password invalues.yaml),hpa.yaml,_helpers.tpl.
Local Contracts
Chart.yaml'sappVersionis one of the four files checked byscripts/quality/check_version_consistency.py(alongsideVERSION,pyproject.toml,simplenote_mcp/__init__.py) — keep it in sync; never bump manually outside the release workflow.values.yaml'simage.tagis not covered bycheck_version_consistency.pyorscripts/validate-helm.py(the latter only checksvalues.yamlfor security settings) — it can silently drift behindChart.yaml'sappVersion. Check it manually when bumping versions.- No real credentials in
values.yamlor any committed values file —secret.yamlexpects.Values.simplenote.passwordto be supplied at install time (--setor a separate, untracked values file).
Verification
python scripts/validate-helm.pyhelm lint helm/simplenote-mcp-server
Child DOX Index
None.
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
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.