Skip to main content

grabdeeznust

gdn for short. MCP server + CLI that lets any agent harness submit a NUST LMS lab by harvesting a friend's already-submitted work and re-skinning it under the user's own identity.

The "agent" is whatever LLM is driving the harness — Claude Code, OpenCode, Cursor, Cline, Continue, Zed, the Anthropic SDK, etc. grabdeeznust only provides the deterministic plumbing: log into the LMS, download submitted files, re-render a styled report.docx, log back in as the user and upload it.

Two LMS accounts are involved:

  • Account 1 — the user's own account; submissions are uploaded here
  • Account 2 — a friend's account; their already-submitted files are harvested here

NUST LMS assignment URLs are the same on both accounts, so the user supplies the URL once and the tool reuses it.

Install

pipx install grabdeeznust
gdn setup

gdn setup walks you through a one-time onboarding:

  1. Prompts for both LMS account credentials (passwords are hidden).
  2. Prompts for the identity values (IDENTITY_NAME, IDENTITY_ROLL, IDENTITY_TERMINAL) that get stamped into every report.
  3. Saves it all to ~/.gdn/.env with mode 0600.
  4. Downloads Playwright's Chromium (~150 MB, one-time).
  5. Prints the MCP config block to paste into your agent harness.

Run gdn doctor any time to check that everything's still in place.

From source (dev)

git clone https://github.com/ZaynIkhlaq/grabdeeznust
cd grabdeeznust
uv sync
uv run gdn setup

A .env in the repo root takes precedence over ~/.gdn/.env, so dev work doesn't pollute your real config.

Add one block to your harness's MCP config.

Claude Code (~/.claude/mcp.json or per-project .mcp.json):

{
  "mcpServers": {
    "gdn": {
      "command": "gdn",
      "args": ["mcp"]
    }
  }
}

Or via the CLI: claude mcp add gdn -- gdn mcp.

OpenCode, Cursor, Cline, Continue, Zed, Claude Desktop — same shape, in their respective MCP settings file. Any MCP-aware client works.

The agent now has these tools:

Tool Purpose
gdn_harvest(url) Login as account 2, download every submitted file at URL
gdn_extract(source_path) Dump docx/pdf/zip/code as plain text
gdn_render(plan, out_path) Render plan dict → styled docx (auto-verified)
gdn_verify(docx_path) Identity check on an existing docx
gdn_submit(url, files) Login as account 1, remove old draft, upload files

And these resources for the agent to fetch context:

  • gdn://briefing — full operator briefing (CLAUDE.md content)
  • gdn://schema — plan dict schema + tone rules (prompts/system.md)

Use it as a plain CLI

If you'd rather drive each step manually:

gdn harvest <URL>                          # account 2 downloads files
gdn extract <source-file>                  # source → plain text
# write work/<slug>/plan.json (schema in prompts/system.md)
gdn render plan.json --out report.docx     # plan → styled docx + verify
gdn submit <URL> <file1> <file2> ...       # account 1 uploads

Browser is visible by default so you can watch. Pass --headless before the subcommand to hide it.

How the report is generated

The browser side is fully deterministic. The "thinking" step — read the source, write a plan that re-skins the report under the user's identity in a student-tone voice — is performed by the LLM driving the harness, not by any baked-in API call. That keeps grabdeeznust provider-neutral: no Anthropic key, no OpenAI key, nothing to configure beyond the LMS creds and the identity values.

The plan is just a JSON dict matching the schema in prompts/system.md. The renderer is pure Python (python-docx) and styles the docx to match the format Claude.ai's web app produces:

  • Arial 11pt body
  • Courier New 9pt code blocks on dark #1E1E2E (the "fake terminal" look)
  • Courier New 9pt output blocks on light green #F0FFF0
  • Section headings (Introduction / Task N / Conclusion) bold 17pt with bottom rule
  • Italic captions on light-blue #EBF3FB panel with a thin blue border

Anything that looks like an AI tell (Claude, Anthropic, as an AI, language model) trips the verifier and blocks render.

Layout

agent.py             # CLI dispatcher
browser.py           # Playwright NUST LMS driver (selectors pinned at top)
report.py            # source extraction + docx rendering + verification
mcp_server.py        # FastMCP wrapper exposing the above as MCP tools/resources
prompts/system.md    # plan-schema + tone guide for whichever LLM is driving
CLAUDE.md            # operator briefing (read by Claude Code)
AGENTS.md            # pointer to CLAUDE.md (read by OpenCode and others)
work/<slug>/         # per-run scratch (source, plan.json, report.docx, error.png on failure)

Notes

  • Selectors live in one block at the top of browser.py. Tweak there if NUST LMS changes its DOM.
  • "Screenshots" in the report are styled text captions ending in (${IDENTITY_TERMINAL}). No code execution, no real images.
  • GDN_WORK_DIR env var overrides where harvest writes scratch files (default: ./work).

Metadata

Release files for grabdeeznust 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for grabdeeznust 0.1.1
File Size Uploaded Provenance Actions
grabdeeznust-0.1.1.tar.gz 18.5 kB With provenance Details for grabdeeznust-0.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for grabdeeznust 0.1.1
File Interpreter ABI Platform Actions
grabdeeznust-0.1.1-py3-none-any.whl Python 3 none any Details for grabdeeznust-0.1.1-py3-none-any.whl

Total release size: 36.6 kB

Release files / grabdeeznust-0.1.1.tar.gz

Download URL grabdeeznust-0.1.1.tar.gz
Size 18.5 kB
Tags Source
SHA-256 checksum
How to use checksums
4107540aefb65d98c0f8290324b9df07c952f44560140287ce0f1f6a1742a66e
BLAKE2b-256 checksum
How to use checksums
842e06cfd7e4d129872952149b7d4645e810d3a3089289983d40d0e222c637f8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 30, 2026.

Transparency log

Release files / grabdeeznust-0.1.1-py3-none-any.whl

Download URL grabdeeznust-0.1.1-py3-none-any.whl
Size 18.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d060d8c0f0f16d9888687fb31cdb878381bb4497177e72eb5bf9eba7dc5a54eb
BLAKE2b-256 checksum
How to use checksums
e54261b41bf1d6d2d196ead78bbeb66c7c68a1e5ac625f55a01cff2a6711b28b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 30, 2026.

Transparency log

Security for grabdeeznust 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for grabdeeznust-0.1.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Apr 30, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page