Weekly scan of agent config files for planted commands
Once a week a read only script hashes every skill, hook, instruction file and MCP config your coding agents load and reports only what changed since the baseline you approved. The agent then reads each new item and says whether it looks malicious, suspicious or benign.
What it does
- Scans agent folders and project instruction files for new or changed items
- Flags download and run commands, credential reads, persistence and hidden characters
- Compares against the baseline you approved and lists only the differences
- Writes a weekly report with a verdict and reason per item
Your approval boundaries
Creates draftsThese actions always wait for your yes:
- Approving a new baseline
- Editing or removing any skill or hook
You decide what happens next.
More about this workflow
This setup is for developers and small engineering teams who want fewer chores. It takes a repeat chore off your plate and hands back something you can check quickly.
First, it scans agent folders and project instruction files for new or changed items. Next, it flags download and run commands, credential reads, persistence and hidden characters. Then it compares against the baseline you approved and lists only the differences. Finally, it writes a weekly report with a verdict and reason per item. It works with your git host, each on its own login with limited access.
You get the prep work done and waiting for you. The agent stops and asks for your yes before approving a new baseline and editing or removing any skill or hook, and says plainly if a step cannot be undone.
“Scheduled runs only report.”
Explore required tools and model recommendations
Tools and access
GitHub
Handles the git host part of this job. Grant a fine-grained token, read code and write comments.
API required: Yes. Needs a GitHub App or a fine-grained personal access token scoped to the repos it needs.
Official links only. Not sponsored, no affiliate links.
Model recommendations
Best pick
Claude Opus 5.5
Its maker points to it for long running coding work.
$4 per million input tokens, $20 per million output tokens.
Anthropic docs as of October 11, 2026
Cheaper backup
Claude Sonnet 5.5
Half the price per token and still strong for reviews and docs.
$2 per million input tokens, $10 per million output tokens.
Anthropic docs as of October 11, 2026
Our own picks. Not sponsored, no affiliate links.
Build your prompt
Add your details, then copy the prompt into your tool.
2Your prompt
4 of 4 still emptyYour answers stay in this browser only.
Run your workflow
Connect your tools with only the access this setup needs, then follow these steps.
Steps
Do these in order. Test on old data before it touches live work.
- 1Connect GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
- 2Paste the prompt where your harness takes instructions. See the note under the Copy button.
- 3Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
- 4Read its log after the first real run. Only widen access once a week of runs looks clean.
Safeguards and trust score
The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.
Writes drafts and notes inside your tools, nothing leaves on its own.
Waits for a yes on: approving a new baseline, editing or removing any skill or hook.
Leaves drafts you can throw away, with a record of what it made.
Runs on its own login across 1 tool. Fewer connections means a smaller blast radius.
How to raise it
This setup is already at its best possible score under our rubric. Nothing left to raise.
Reviewed by Trustcase (example setup). How scoring works
Embed badge
Show this trust score on your site or README. It links back here.
[](https://trustcase.dev/use-cases/weekly-scan-of-agent-config-files-for-planted-commands)<a href="https://trustcase.dev/use-cases/weekly-scan-of-agent-config-files-for-planted-commands"><img src="https://trustcase.dev/badge/weekly-scan-of-agent-config-files-for-planted-commands.svg" alt="Trustcase trust score for Weekly scan of agent config files for planted commands" height="20"></a>More engineering workflows
- Pull request reviewer
Gives every PR a first pass before a person looks.
- Flaky test hunter
Finds tests that fail at random and why.
- Incident timeline
Builds the timeline during an outage so people can focus on the fix.
- Dependency updater
Keeps packages current without surprise breakage.
Other workflows that use the same tools
- Site change tester
Marketing. Tries small edits to your site, watches whether more visitors stay, and keeps only the changes that help. Good for steady small wins on a landing page.
- Daily kids lesson builder
Personal. Builds a short interactive lesson for your kids each night and has a second agent check it. You read a review email and approve it before the kids get the link.
- Weekly delivery status report
Operations. Pulls your team's work items once a week and builds a status report grouped by initiative. It puts at risk items first and flags anything with no update in two weeks.