docs(prompts,skills): bound recon output for shared-disk hygiene#783
Merged
Conversation
Add lightweight, always-on disk-hygiene guidance so agents keep recon artifacts bounded on the shared /workspace instead of writing very large uncapped crawl output. - system_prompt.jinja: DISK & SCRATCH HYGIENE note in the shared-workspace block; recon PHASE 1 crawl bullet asks to bound each crawl and tidy up. - skills/tooling/katana.md: bound the baseline/deep examples with -ct, add a Keeping-output-manageable note (bound by -ct/-d, reserve -jsl/-kf all for narrowed targets, check du -sh, dedupe and remove raw .jsonl).
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Contributor
Greptile SummaryThis PR adds guidance for keeping reconnaissance output bounded on the shared workspace. The main changes are:
Confidence Score: 5/5This looks safe to merge.
Important Files Changed
Reviews (3): Last reviewed commit: "docs(skills): add research-backed katana..." | Re-trigger Greptile |
Address Greptile review: - system_prompt: only clean up your own task's files; don't delete another agent's files in the shared workspace unless confirmed unused. - katana.md: extract+dedupe URLs with jq before removing raw .jsonl (sort -u on JSONL compares whole records, not URLs).
Contributor
Author
Per projectdiscovery katana docs, add the flags that actually bound crawl output size and a reduce-then-delete workflow: - -mdp (max-domain-pages; default is unlimited), -fsu (filter-similar), -fs scope, -f url (URL-only), -or/-ob (omit raw/body), -mrs. - Baseline now includes -mdp 2000 -fsu; new 'Keeping output small' section: bound scope/volume, shrink records, distil then delete raw crawls.
Contributor
Author
0xallam
approved these changes
Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Agents on a deep black-box scan can write very large, uncapped recon artifacts (e.g.
katanaJSONL crawl output) into the single shared/workspacedisk, with no self-limiting. Nothing in the prompt or the katana skill currently nudges them to bound crawl output or clean it up, so a broad-jsl/-kf allcrawl on a large site can grow until the sandbox disk saturates. This adds lightweight, best-effort guidance (no code/runtime changes) so agents keep recon output bounded and tidy.Layered so the rule is seen regardless of which skills are loaded:
agents/prompts/system_prompt.jinja— always-onDISK & SCRATCH HYGIENEnote in the shared-workspace (AGENT ISOLATION & SANDBOXING) block:/workspaceis shared/finite, prefer bounded recon over "collect everything", send large output to/workspace/scratch/and remove raw output once distilled, and — when disk is tight — clean up only files from your own task (don't delete another agent's in-use artifacts on the shared disk). The PHASE 1 "CRAWL thoroughly" bullet also gains a bound-and-tidy reminder.skills/tooling/katana.md— document the flags that actually bound crawl output size (from projectdiscovery's katana docs) and a reduce-then-delete workflow:-mdp(max-domain-pages — katana's default is unlimited),-fsu(collapse near-identical URLs),-fs fqdn(defaultrdncrawls all subdomains),-f url(plain URL list vs verbose JSONL),-or/-ob(omit raw/body),-mrs(cap per-response bytes).-ct 10m -mdp 2000 -fsu; deep-JS example is time-bounded.-jsl/-kf allfor narrowed targets, then distil (-f url/ short path list) and delete the raw crawl; sanity-check withdu -sh.Intentionally soft in tone (guidance, not hard mandates) and free of specific size thresholds; a model told to "go very deep" can still ignore it, so this is best paired with a hard inner-sandbox disk guard as the real backstop. This PR is the prompt/skill layer only.
Link to Devin session: https://app.devin.ai/sessions/dad023e379e942f287bcf6822463b7a4
Requested by: @0xallam