q-target

A command for creating or updating a profile for a person, organisation, or other investigation target.

In plain words
What is it for?
Use it to maintain a target file, cross-reference related targets, add new events to the master timeline, record collection gaps, and update investigation state.
Why use it?
It keeps identity details, connections, events, collection status, and assessment in one linked record instead of scattered investigation notes.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/assafkip/huntkit/q-target
Clone the repo
git clone --depth 1 https://github.com/assafkip/huntkit
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 139 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00139
Opus 5 $0.00000 $0.00069
Sonnet 5 $0.00000 $0.00028
Haiku 4.5 $0.00000 $0.00014

Measured 2d ago against content hash 8498daa1837a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

q-target scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/q-target.md · 13 lines

What it actually says

Create or update a target profile for an investigation target.

Execute the /q-target steps from .q-system/commands.md.

  1. Create/update investigations/<case>/targets/[name].md using the template from investigations/<case>/targets/_TEMPLATE.md
  2. Populate: identity, digital footprint, connections, timeline, collection status, assessment
  3. Cross-reference against other target files for connections
  4. Update investigations/<case>/timelines/master-timeline.md if new events found
  5. Flag collection gaps
  6. Update memory/investigation-state.md

Argument: $ARGUMENTS (required: target name)

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 13 lines · 0 tokens per session scan A 8498daa1837a

Subscribe to this mod's changes

q-target is a command published in the GitHub repository assafkip/huntkit (51 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 139 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.