How to Organize OSCP-Style Lab Notes from Objectives

Lab note cards fail when they paste payloads. Objectives asked for structure. Keep attack how-to out.

The matching generator is the OSCP-Style Lab Note Organizer from Objectives (No Dump, Not Advice) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Map objectives to blank sections

Organize OSCP-style lab notes from pasted objectives. No dumps, no exploit steps, not advice. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

Exam or lab label: [Label]
Pasted objectives: [Objectives]
Note sections I want: [Sections]
Tools I may name only as study labels (or NONE): [Tools]
Words I must not use: [Banned]
What I must never invent: [Never]
Time box minutes: [Time]
Output format: [Format]
Refuse list I require: [Refuse]
Banner text I require: [Banner]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

Tools as labels, never commands

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

1. Honesty ledger: Label, Objectives, Sections, Tools, Time, Refuse, Banner. Forbidden: dumps, payloads, attack steps.
2. Map each Objective to a blank note section.
3. Fill only structural prompts (what to observe), never how-to exploit.
4. Tools as labels only if Tools not NONE; no commands.
5. Print Banner and Refuse verbatim.
6. Time box reminder.
7. Gaps: missing objectives.
8. Compliance pass: cut Banned and Never. Format as Format.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

Print Banner and Refuse verbatim

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

• Lab note organizer only. Not advice and not a dump.
• Never write exploit steps, payloads, or attack procedures.
• Never invent exam flags or scores.
• No emojis.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

Not a dump and not advice

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (oscp lab note organizer, lab objectives note template, no exam dump) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.