What is discord-user-awareness?

A Discord identity guide for resolving human members and interpreting @mentions, which are messages that directly tag users, roles, or channels. It distinguishes the bot operator, other allowed users, the bot itself, and non-user mentions.

Use it before allowlisting, removing, timing out, or otherwise targeting a Discord member, especially when the request uses a name, vague wording, or an @mention.

It prevents moderation or access actions from targeting the wrong account. It also explains which stable numeric Discord user ID to use for allowlists and moderation commands.

discord-user-awareness — Skill by Yamato-main/gemini-discord

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.

Any agent

npx skills add Yamato-main/gemini-discord --skill discord-user-awareness

Clone the repo

git clone --depth 1 https://github.com/Yamato-main/gemini-discord

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/yamato-main/gemini-discord/discord-user-awareness/github.svg)](https://agentmods.dev/skills/yamato-main/gemini-discord/discord-user-awareness)

Your own site

<a href="https://agentmods.dev/skills/yamato-main/gemini-discord/discord-user-awareness"><img src="https://agentmods.dev/badge/skills/yamato-main/gemini-discord/discord-user-awareness/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/yamato-main/gemini-discord/discord-user-awareness"><img src="https://agentmods.dev/badge/skills/yamato-main/gemini-discord/discord-user-awareness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 692 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00052	$0.00692
Opus 5.5	$0.00021	$0.00277
Sonnet 5.5	$0.00010	$0.00138
Haiku 4.5	$0.00005	$0.00069

Measured 2mo ago against content hash 64f40088d6aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

discord-user-awareness 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 2mo 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.

skills/discord-user-awareness/SKILL.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Discord user awareness

Boss vs guest allowlist (critical)

Setting	Who	Powers
`DISCORD_BOSS_USER_ID`	One human operator	Full bridge: user discovery, allowlist, admin, moderation
`DISCORD_ALLOWED_USER_IDS`	Other humans	Chat only when guests are disabled — no user lists, no admin tools

Never put the bot's user ID in either field. Putting the bot on the guest allowlist does not give it admin powers — it only pollutes config.

When to use

The user wants to add or remove someone from the guest allowlist.
The request refers to another person, "the other user", a display name, or a vague target.
You need a stable numeric Discord user ID for allowlist_add, kick, or timeout.
The message includes @ pings and you must not confuse users, roles, channels, @everyone/@here, or this bot.

@ mention rules

Every incoming Discord message includes a [Mentions] block. Trust it over guesswork:

Signal	Meaning
User pings	Real `<@userId>` mentions — humans or bots, each with a stable id
This bot	Your bridge identity — never "the other user"
Role pings	`<@&roleId>` — not a user; do not allowlist or moderate as a person
Channel refs	`<#channelId>` — use channel discovery, not user discovery
@everyone / @here	Broadcast only — not a specific member
Plain `@Name` in text	Not a ping unless it appears under User pings

When the user says "the other user" while pinging you, the target is a different human from the User pings list (or run users discovery).

Workflow

Run discord_admin with action status if you do not already know the bot's own ID (shown as Bot: name (id)).
Run discord_admin with action users. Pass query when the user named someone or you need to narrow the list.
Pick a human from the Humans section. Never use an ID from Bots or the bot's own ID from status.
Run allowlist_add or moderation with the resolved user_id.

Read the full file on GitHub · 56 lines

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.

2mo ago First seen · 56 lines · 52 tokens per session scan A 64f40088d6aa

Subscribe to this mod's changes

discord-user-awareness is a skill published in the GitHub repository Yamato-main/gemini-discord (5 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 692 once invoked, about $0.0002 per session on Opus 5.5. 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-31.

TypeScript discord discord-bot gemini-cli gemini-cli-extension mcp

discord-user-awareness next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
discord-user-awarenessYamato-main/gemini-discord	Skill	5	yesterday	MIT	A	52	Claude Code, Codex
nodejs-keccak256Jamkris/everything-gemini-code	Skill	93	5mo ago	MIT	A	51	Claude Code, Codex
nestjs-patternsJamkris/everything-gemini-code	Skill	93	5mo ago	MIT	A	33	Claude Code, Codex
bun-runtimeJamkris/everything-gemini-code	Skill	93	5mo ago	MIT	A	34	Claude Code, Codex
npm-packageremorses/kimaki	Skill	1.4k	yesterday	MIT	C	78	Claude Code, Codex
novel-archivingwanikua/danghuangshang	Skill	2.7k	5mo ago	MIT	A	44	Claude Code, Codex
novel-memorywanikua/danghuangshang	Skill	2.7k	5mo ago	MIT	A	51	Claude Code, Codex