Follow another Bluesky account, like a post, and repost a post, then undo each of those three actions by deleting the corresponding record.

Documented steps

1. To follow: build an app.bsky.graph.follow record {"$type": "app.bsky.graph.follow", "subject": "<DID of the account to follow>", "createdAt": "<timestamp>"}. subject must be a DID string, not a handle - resolve the target handle to a DID first via com.atproto.identity.resolveHandle if needed.
2. To like: build an app.bsky.feed.like record {"$type": "app.bsky.feed.like", "subject": {"uri": "<post at:// uri>", "cid": "<post cid>"}, "createdAt": "<timestamp>"} - subject here is a strong reference (uri+cid) to the target post, not just a DID.
3. To repost: build an app.bsky.feed.repost record with the identical shape to a like: {"$type": "app.bsky.feed.repost", "subject": {"uri": ..., "cid": ...}, "createdAt": ...}.
4. Create any of the three via POST $PDSHOST/xrpc/com.atproto.repo.createRecord with body {"repo": "<your-did>", "collection": "app.bsky.graph.follow" | "app.bsky.feed.like" | "app.bsky.feed.repost", "record": {...from steps 1-3...}}. The response's 'uri' field's last path segment is the rkey you'll need to undo the action.
5. To undo any of the three, POST $PDSHOST/xrpc/com.atproto.repo.deleteRecord with body {"repo": "<your-did>", "collection": "<same collection as creation>", "rkey": "<rkey from the create response's uri>"}. repo, collection, and rkey are all required; deleteRecord is idempotent (also succeeds if the record no longer exists).
6. Optionally pass swapCommit (expected current repo commit CID) or, for deleteRecord, swapRecord (expected CID of the record being deleted) to both createRecord and deleteRecord for compare-and-swap safety against concurrent writes.
7. Duplicate follows of the same account are ignored by the AppView, per the app.bsky.graph.follow Lexicon description, so re-following an already-followed account is safe but still consumes a CREATE write against your rate-limit budget.