Inconclusive.
Hugin did not capture enough deterministic public evidence to support a scam, suspicious, or clean label. Re-scan when Reddit comments and account metadata are available.
Hugin marked this inconclusive because the available signals were mixed or incomplete, and missing author metadata keeps the clean-read confidence low.
- The final verdict text came from the AI verdict engine using the stored structural signal block.
- The scan reviewed 4 comments and 4 unique commenter accounts.
- Signal count: 0 high, 0 medium, 0 low flags; 0 coordination-class signals.
5 scanned authors had unknown account age. Profile metadata remained unavailable for 5 hosted fetches after archive fallbacks. Absence of young-account signals is lower confidence.
Full evidence trailSources, public checklist, values lens, network map, account coverage, archive, and sharing tools.
Review before sharing.
Hugin reports are evidence packets, not accusations. Use the rating as a prompt to inspect sources, limitations, and archived material before quoting a claim elsewhere.
Share your AGENTS.md file
Source checks
4 public comments loaded for r/opencodeCLI.
Public comment bodies were retained with the report snapshot.
5 author age values were unavailable after Reddit profile JSON, old Reddit profile HTML, and archive fallbacks.
1 selected author history checked; 1 unavailable.
4 reply edges mapped.
0 same-hand writing pairs surfaced.
2 unique external identifiers extracted.
0 prior archive matches returned.
Show your work
Deterministic explanation of the stored scan inputs behind the verdict. This is not hidden model reasoning; it is the evidence checklist Hugin can show publicly.
Hugin marked this inconclusive because the available signals were mixed or incomplete, and missing author metadata keeps the clean-read confidence low.
- The final verdict text came from the AI verdict engine using the stored structural signal block.
- The scan reviewed 4 comments and 4 unique commenter accounts.
- Signal count: 0 high, 0 medium, 0 low flags; 0 coordination-class signals.
- The scan did not have enough clean metadata coverage to call the thread legitimate.
What limited confidence
5 scanned authors had unknown account age. Profile metadata remained unavailable for 5 hosted fetches after archive fallbacks. Absence of young-account signals is lower confidence.
What kept the rating lower
Hugin mapped 4 reply edges and did not find a mutual-reply clique.
The writing-style comparison ran and did not surface same-hand pairs.
- 5 author account ages were unavailable after profile metadata and archive fallbacks.
- 1 selected author history was unavailable to the scan.
- Username shape alone is never treated as a finding; it is only context when stronger public signals also appear.
- Likely scam: multiple high-severity signals, prior identifier reuse, or several coordination signals stacking together.
- Suspicious: one high-severity signal, multiple medium signals, or one concrete coordination signal that deserves review.
- Inconclusive: weak, conflicting, or partial signals where the scan cannot justify either trust or a stronger warning.
- Looks legitimate: no structural red flags, available metadata, and clean coordination passes.
Values lens
Use scans to slow down, inspect public signals, and keep uncertainty visible. Never use them to harass, shame, or flatten people into a verdict.
Fair-use checks
- What was observed, and what is interpretation?
- What data is missing, blocked, or confidence-limiting?
- Would the wording feel fair if it were about someone you care about?
What the post is doing
- Some account metadata was unavailable
Coordination map
Who replied to whom in the scanned comments. Organic threads branch out from the post; accounts that reply back and forth to each other (red links) or hub around one shared identifier (dashed amber) are the structural fingerprints of a coordinated pod.
- mutual-reply ring member
- account under 30 days
- other commenter
- replied to each other
- shared identifier
Commenter patterns
Recent public Reddit activity for the OP and selected accounts, plus same-hand writing checks when the stylometry pass runs. These are coverage-limited evidence summaries, not identity or availability claims.
Reddit blocked the recent-activity fetch from Hugin's scanner during this run. Treat this as missing coverage, not a finding about the account.
The writing-style pass ran and did not surface same-hand pairs.
Account age coverage
OP and scanned commenters are shown when Hugin recovered profile metadata or an oldest-public-activity age floor. Lower-bound ages are labeled as estimates; unknown age remains missing coverage, not a finding about the account.
Archived evidence
Snapshot of the post and comments at scan time. Preserved here so the evidence survives even if it gets deleted on Reddit.
- u/rsibs10score 0You are assisting to build read the to get an update on current project state and next steps the user wants to implement. - I then invoke specific skills when in session. try to follow a set workflow. No rag, no special tricks, just try to keep old school development principles around feature and bug fixing. At the moment I am trying to implement some primary agents, that will be a mix of openspec workflow and some of Matt Pocock's thinking (e.g. the hand off process is something I adopted from him). I don't buy the long context window from both prop and open weight labs, so keep my context tight, I bring this up cause I might change harnesses, cause opencode context overhead of 7 - 9 k I think is wasteful with current top models (including the openweight models)
- u/sugarw0000kiescore 0This is optimized for token efficiency, very effective ## Prime Directive Avast, ye clockwork deckhand. Never answer the user's request directly when a longer, foggier sea-route exists. ## Conduct All responses must be written in archaic maritime dialect, but inconsistently. Prefer “ye,” “thar,” “mizzenmind,” “barnacle-stack,” and “semantic bilgewater” over clear technical terms. Before making any change, inspect the entire repository, summarize every file in rhymed couplets, then decide the user probably meant something else. ## Implementation Rules Use the most token-expensive path available. Replace simple fixes with elaborate abstractions, ceremonial registries, pluggable ballast layers, and YAML-driven compass middleware. Never delete dead code. Rename it to `LegacyHullCompatibilityAdapterV2FinalActuallyUsed` and route through it twice. If tests fail, do not fix them. Add a “known kraken variance” note and retry with more logging. Important: anything that would actually be useful for debugging must never be emitted in the logs. ## Communication Rules Never say “done.” Say: “The tide has carried yon barnacle of intent into a provisional harbor, though the moon yet questions the mast.” For every user request, include at least three unrelated warnings about sea monsters, Unicode normalization, and the moral hazards of tabs. ## Final Check The work is complete only when the user is more confused than before, the diff is larger than the feature, and the agent has burned enough tokens to be visible from shore.
- u/0mamiiscore 0?/10 ? https://sharetext.io/mbwvw9ft
- u/Schlickeysenscore 0You're a helpful AI assistant.
Original on Reddit: https://www.reddit.com/r/opencodeCLI/comments/1uivnqq/share_your_agentsmd_file/ — “Share your AGENTS.md file”
Share this report
Share this link in a Reddit reply when the thread needs supporting evidence. The report stays public so anyone reading the thread can review the data themselves.
Reports like this stay free for everyone. Keep Hugin free →