Add NeatContext to Development & Workflow

[tanglearncode]

Submitting NeatContext, as invited in XTSoftwareLabs/neatcontext-plugins#94. Thanks for the offer.

Extension

NeatContext — MIT, actively maintained (current release v0.3.5).

The durable knowledge from a long agent session — how a system actually behaves, what an investigation ruled out, why a decision went the way it did — is produced as a side effect of the work and then thrown away with the transcript. NeatContext extracts that knowledge and saves it as a structured context: a domain profile plus a knowledge folder, not the raw conversation. Reconnect the context in a later session and the agent starts with what it needs; share the folder and a teammate starts there too. /neatcontext:save writes or updates a context, /neatcontext:use connects one, and sessions can route themselves to the right context in auto or ask mode.

Category

Community Plugins → Development & Workflow, inserted between memi and Ontoly.

It could also have gone under Kimi Plugins — the repository ships a root kimi.plugin.json and installs with /plugins install https://github.com/XTSoftwareLabs/neatcontext-plugins. I put it in the main section because NeatContext is not Kimi-specific: it ships host integrations for Claude Code, Codex, GitHub Copilot, Kimi Code, and pi from one repository, which reads like the multi-host entries already in Development & Workflow. Happy to move it or add a second entry if you would rather have it listed under Kimi.

Verification

Installed and exercised on Claude Code:

claude plugin marketplace add https://github.com/XTSoftwareLabs/neatcontext-plugins.git
claude plugin install neatcontext@neatcontext --scope user

Scanner run against a clean clone with the thresholds from CONTRIBUTING.md:

$ plugin-scanner scan . --min-score 80 --fail-on-severity high
Local plugins scanned: 2
Findings: critical:0, high:0, medium:19, low:11, info:32
Final Score: 85/100 (B - Good)
exit 0

Scanner CI is being added to the source repository in XTSoftwareLabs/neatcontext-plugins#97 — .github/workflows/plugin-scanner.yml, running hashgraph-online/ai-plugin-scanner-action on push and pull_request with min_score: 80 and fail_on_severity: high, both actions pinned to a commit SHA and the job limited to contents: read. Since validate-contribution.py reads the source repository's default branch, this PR's scanner check will only go green once that lands; I will comment here when it does, and it would be worth a re-run then.

One note on the scan, since it is visible in the report: the repository also commits a .plugin-scanner.toml that suppresses HARDCODED_SECRET and SHELL_INJECTION_PATTERN under its test directories only. The seven high findings the scanner reports there are all in test files — fixtures holding deliberately fake credentials, because the assertion is that NeatContext keeps material like that out of a saved context, and spawn(process.execPath, [script, ...args]) calls, which are the structured-argument form the rule's remediation asks for. Both rules stay live on all shipped source: no file under any src/ or shared/ is matched by the ignore patterns. Flagging it up front rather than leaving you to find it in the diff — happy to talk it through if you would rather see it handled another way.

python3 scripts/check-alphabetical.py README.md passes locally.

[github-actions]

✅ Contribution check passed. @tanglearncode, catalog validation succeeded.

scan passed

All 1 source-repository scanner job(s) passed. Catalog validation passed.
View the latest sweep.

[github-actions]

🎉 Hey @tanglearncode, your plugin has been merged and is now listed in the HOL Registry!

Claim your plugin

As the author, you can verify ownership of your plugin to unlock:

• Owner-verified badge on your plugin's registry listing
• Trust score visibility and analytics for your plugin
• Direct claim link to share with your community
• Dashboard access at hol.org/guard/plugins to track installs, trust, and engagement

How to claim

1. Visit hol.org/guard/plugins
2. Find your plugin and click "Verify ownership"
3. Sign in with GitHub — we only request read:user, user:email, and read:org (no write access to your repos)
4. We verify you own the repository, and your plugin gets the ✅ owner-verified badge

The whole process takes under 30 seconds. No need to add any secrets or tokens to your repo — verification is done entirely through GitHub OAuth.

If you have any questions, feel free to ask here or reach out at support@hol.org.

[kantorcodes]

Hi @tanglearncode — a quick follow-up about your plugin xtsoftwarelabs/neatcontext-plugins.

The listing is live in the HOL Registry, and ownership verification is still available at HOL Guard.

Verifying ownership takes about 30 seconds and unlocks the owner-verified badge, plugin analytics, and the author dashboard. Sign in with GitHub; no repository write access is needed.

We may follow up again later if ownership verification is still incomplete.

If you already completed verification, no action is needed — the next scheduler run will stop these reminders.